New task
Laravel conventions, as agent skills. Your team's rulebook — portable across Claude Code, Codex, Cursor, and anything else SKILL.md.
npx -y skills add fbarrento/laravel-agent-kit --skill new-taskAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Creates a fresh task branch from the latest remote main branch using conventional-commit branch naming. Use when starting any new coding task, bug fix, refactor, feature, chore, documentation change, or user request that will modify repository files.
SKILL.md
1.8 KB, 354 tokens by cl100k_base, as published. Nobody here has run it
Fresh Task Branch
Quick Start
Before modifying repository files for a new task, start from a fresh branch based on origin/main:
git fetch origin
git switch --create feat/short-description origin/main
Workflow
- Check the current branch and working tree with
git status --short --branch. - If there are uncommitted changes, do not switch branches or modify them without asking the user how to proceed.
- Fetch the latest remote refs with
git fetch origin. - Create the task branch from
origin/main, not localmain. - Use a branch name aligned with conventional commits.
- Continue with the requested implementation only after the fresh branch is active.
Branch Naming
Format: type/kebab-description. The type vocabulary (feat, fix,
refactor, chore, docs, test, …) and naming rules are owned by the
git-conventions skill — use it as the canonical source so branch,
commit, and PR names stay aligned. This skill does not restate the vocab.
Lowercase kebab-case after the prefix, short and specific, for example
fix/waitlist-validation or chore/upgrade-laravel-12.
Guardrails
- Never overwrite, reset, delete, stash, or commit user work without explicit approval.
- If the requested task continues existing branch work, ask whether to stay on the current branch instead of creating a new one.
- If
origin/mainis unavailable, inspect remotes and ask before choosing another base branch. - Do not create a new branch for purely informational questions, reviews, or planning unless the user asks for file changes.