Menu
Git practices for this project. USE WHEN committing code OR creating commits OR git operations. Enforces clean git history.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
PRD lifecycle from vague idea to structured spec. USE WHEN design product OR write PRD OR review PRD OR structure PRD OR restructure PRD OR validate PRD OR check consistency OR verify PRD OR run checks OR one-pager OR "too complex" OR complexity signals OR split PRD OR process findings OR fix findings OR go through findings.
Create, validate, and optimize Claude Code skills. USE WHEN user says "skill" + intent (create, make, build, want, need, help me with) OR "workflow" + intent (create, make, add, new) OR "workflow for/to" OR "automate [task]" OR mentions skill structure, validate, audit OR optimize workflow OR improve workflow OR analyze session OR workflow delta.
Extract insights and patterns from YouTube coding videos and their GitHub repos. USE WHEN analyze video OR learn from video OR extract lessons OR video insights OR IndyDevDan OR agentic engineer video.
Drive multi-step plan implementation with focused context packets. USE WHEN step prepare OR step check OR step execute OR step validate OR step fix OR step done OR implementation workflow OR plan packet.
Create, modify, review, and harden agentic prompts/slash commands. USE WHEN create prompt OR new command OR slash command OR modify prompt OR update workflow OR improve prompt OR edit prompt OR prompt structure OR workflow prompt OR skill workflow OR add workflow to skill OR workflow file OR write workflow OR review prompt OR harden prompt OR add validation OR add hooks OR self-validation OR validate agent OR add self-validation. Guides through 7 prompt levels with proper sections.
Expert guidance for creating, writing, and refining Claude Code Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices.
| name | UseGit |
| description | Git practices for this project. USE WHEN committing code OR creating commits OR git operations. Enforces clean git history. |
Enforces clean git practices and commit hygiene for this project.
One commit = one logical change.
Commit after each step, then STOP and wait for user.
| Workflow | Trigger | File |
|---|---|---|
| PreCommit | Before running git commit | Workflows/PreCommit.md |
| Rule | Command |
|---|---|
| File renames | git mv (not mv) |
| File deletions | git rm (not rm) |
| Run commands from | Repo root (use git rev-parse --show-toplevel) |
| Before staging | Always run git status first |
| Staging vs committing | Separate git add and git commit commands |
Example 1: After completing a feature step
[Implementation done, tests pass]
→ git status
→ git add [files]
→ git commit -m "feat: ..."
→ STOP and wait for user
Example 2: Renaming a file
→ git mv old-name.ts new-name.ts
→ git commit -m "refactor: rename ..."
Example 3: Multiple logical changes found
[About to commit, notice unrelated changes]
→ STOP
→ Use git add -p to stage only related changes
→ Commit each logical change separately