القائمة
Create a git worktree and prime the development environment for a new feature or refactor. Use when starting isolated feature work or needing a separate working copy.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Diagnose and fix a failed GitHub Actions job run. Given a run URL/ID (or the latest failed run on the current branch), pulls the failure via the gh CLI, reproduces it in an isolated worktree off the exact failing commit, fixes it, and verifies locally. Use when the user says "fix the failing CI", "the GitHub Action failed", invokes "/fix-ci", or points at a failed GitHub Actions run.
Reviews code for bugs, security vulnerabilities, and quality issues. MUST be invoked automatically after completing a coding task (feature, bug fix, or refactor) - do not wait for user to request it. Also use when the user asks to review changes, check a diff, or look over a branch/PR before committing.
Reflect on the current session to find mistakes, user corrections, ambiguous instructions, and failures — then propose durable root-cause fixes to the project's instruction docs (CLAUDE.md, .claude/rules, .claude/skills) so they don't recur. Use when the user asks to reflect on the session, run a retro/postmortem, capture lessons, or after a session with notable corrections or repeated mistakes.
Create Knex database migrations for the Benefriches API. Use when adding, modifying, or removing database columns/tables. Handles schema changes (create table, add/drop/rename columns), data migrations, and updates to tableTypes.d.ts.
Run Benefriches end-to-end tests with automatic Docker stack lifecycle management. Starts the e2e docker-compose stack, waits for readiness, runs Playwright tests, and tears down the stack on success. Use when the user asks to run e2e tests, end-to-end tests, or invokes /run-e2e-tests. Accepts an optional argument to focus on specific tests (e.g., tests/create-site/ or a specific spec file).
Implement a feature plan from a spec file, following test-first methodology and tracking all deliverables. Use this skill whenever the user says "implement this plan", "start working on specs/...", "let's build the feature from the spec", "execute the plan", or points at a plan file and says to build it. Don't wait for explicit "implement-plan" keywords.
| name | worktree |
| effort | low |
| model | haiku |
| description | Create a git worktree and prime the development environment for a new feature or refactor. Use when starting isolated feature work or needing a separate working copy. |
| allowed-tools | Bash |
| user-invocable | true |
Create a new git worktree for isolated feature development.
The script always creates a new branch from current HEAD, places the worktree under .claude/worktrees/<name> (gitignored, so it never pollutes git status/diff/search), and primes it (pnpm install, shared build, env files):
scripts/create-worktree.sh <branch-name>
If the user provides just a feature name without a prefix, add the appropriate prefix:
feat/<name> (default)refactor/<name> (if user mentions "refactor")fix/<name> (if user mentions "fix" or "bug")chore/<name> (if user mentions "chore")| User Input | Branch Name |
|---|---|
/worktree new-feature | feat/new-feature |
/worktree refactor auth | refactor/auth |
/worktree fix/login-bug | fix/login-bug (keep as-is) |
/worktree feat/my-thing | feat/my-thing (keep as-is) |
Tell the user:
cd <worktree-path>$ARGUMENTS