A collection of 18 Claude Code custom skills for structured development workflows.
| Skill | Command | Description |
|---|---|---|
| commit | /commit |
Emoji-prefixed git commits with optional push |
| catchup | /catchup |
Summarize uncommitted changes in the working tree |
| epic | /epic |
Generate structured epics with interactive approval phases |
| write-prd | /write-prd |
Write a PRD through interview, file as GitHub issue |
| tdd | /tdd |
Red-green-refactor TDD with vertical slices |
| prd-to-plan | /prd-to-plan |
Convert a PRD into phased vertical-slice implementation plan |
| triage-issue | /triage-issue |
Investigate a bug, find root cause, file GitHub issue with TDD fix plan |
| qa | /qa |
Rapidly file well-structured GitHub issues |
| grind | /grind |
Work through open issues with TDD, feature branches, and PRs |
| prd-to-issues | /prd-to-issues |
Break a PRD into vertical-slice GitHub issues |
| git-guardrails | /git-guardrails |
Set up hooks to block dangerous git commands |
| grill-me | /grill-me |
Stress-test a plan or design through relentless interview; uses the project glossary when present |
| terms | /terms |
Build & maintain a project's ubiquitous-language glossary (CONTEXT.md), ADRs, and context map |
| e2e-setup | /e2e-setup |
Scaffold Playwright E2E testing with auto-detection |
| code-quality | /code-quality |
Apply the Code Quality Playbook baseline (Prettier, ESLint, husky, CI gate) + optional npm→pnpm migration |
| do-work | /do-work |
Execute a unit of work end-to-end (understand→plan→build→validate→commit) driven by feedback loops |
| rams | /rams |
Accessibility + visual design review in the voice of Rams |
| ffuf-skill | /ffuf-web-fuzzing |
ffuf web fuzzing for authorized pentesting (vendored from jthack/ffuf_claude_skill) |
Several skills interact with GitHub via the GitHub CLI (gh). Skills that require it: /write-prd, /triage-issue, /qa, /grind, /prd-to-issues, /prd-to-plan.
Install gh:
# macOS
brew install gh
# Windows
winget install --id GitHub.cli
# Linux (Debian/Ubuntu)
sudo apt install gh
# Or see https://cli.github.com for all optionsThen authenticate:
gh auth loginSeveral skills automatically assign issues to @me (the authenticated gh user) when creating or listing issues. This affects: /qa, /triage-issue, /prd-to-issues, /write-prd, and /grind.
Each team member should add the following to their ~/.claude/CLAUDE.md to set their GitHub username:
# GitHub Issue Defaults
GitHub username: `<your-github-username>`
**All skills and workflows that interact with GitHub issues MUST follow these rules:**
- **Creating issues** (`/qa`, `/triage-issue`, `/prd-to-issues`, `/epic`, or any `gh issue create`): Always include `--assignee <your-github-username>` unless the user explicitly names a different assignee.
- **Selecting issues to work** (`/grind`, or any `gh issue list` used to pick up work): Always filter with `--assignee @me`. Do not work issues assigned to other people.
- **Closing/finishing issues** (`/grind`, `/commit`, PRs): Only close issues assigned to `<your-github-username>` unless explicitly told otherwise.Replace <your-github-username> with your actual GitHub handle. This ensures each person's skills only create and pick up their own issues.
Other dependencies:
| Dependency | Required by | Install |
|---|---|---|
jq |
/git-guardrails |
brew install jq |
| Node.js + npm | /e2e-setup |
https://nodejs.org |
Each skill is a directory containing a SKILL.md (with name/description frontmatter). Copy the whole skill directory into your skills folder — ~/.claude/skills/ (global) or .claude/skills/ in a project (project-scoped):
cp -R <skill> ~/.claude/skills/Then use the corresponding /command in Claude Code. Each skill's own README has its exact install line.