菜单
Use when performing common development tasks like committing code, reviewing changes, running tests, fixing bugs, creating PRs, or checking repo status. Provides structured workflows for everyday git and development operations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user writes new Python, or asks for review, refactor, or cleanup of Python code, names, comments/docstrings, functions, or tests. Applies Robert Martin's complete Clean Code catalog -- naming, functions, comments, DRY, boundary conditions, and tests -- to the code being changed.
Use when writing code, making git operations, handling secrets, reviewing PRs, or working with dependencies. Enforces git safety, security best practices, PR workflow discipline, and context-efficient development patterns. Auto-activates as guardrails.
Use when reviewing motion quality, adding animation, transitions, hover effects, making the UI feel more alive, or when animations stutter and transitions jank. Covers three modes -- audit motion code against Disney's 12 principles (file:line findings), add purposeful animations and micro-interactions to a feature, or fix animation performance (layout thrashing, compositor properties, scroll-linked motion, blur).
Use when setting up new repositories, auditing existing ones, or preparing repos for public visibility. Generates .gitignore, .env.example, README, and LICENSE files. Detects committed secrets and flags security issues.
Use when the user asks to audit a session for uncaptured learnings. Activates on "audit this session", "session audit", "what did we miss", "end of session check", or "/starter-session-audit". Scans the conversation for corrections, preferences, decisions, and new context, then proposes where to save each.
Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.
| name | dev-workflow |
| description | Use when performing common development tasks like committing code, reviewing changes, running tests, fixing bugs, creating PRs, or checking repo status. Provides structured workflows for everyday git and development operations. |
| Task | Command | What It Does |
|---|---|---|
| Commit | /commit | Stage changes, write conventional commit message |
| Review | /review | Analyze branch changes for bugs, security, quality |
| Test | /test | Detect test framework, run tests, diagnose failures |
| Fix | /fix | Trace root cause, implement minimal fix, verify |
| PR | /pr | Create pull request with summary and test plan |
| Status | /status | Full repo overview: branches, PRs, CI, sync state |
| Check PR | /check-pr | CI status, reviews, comments, merge readiness |
git status and git diff to understand changesgit log --oneline -5 to match the repo's commit styletype: short descriptionfeat, fix, refactor, docs, test, chore, style, perfWhen reviewing branch changes (git diff main...HEAD):
| Category | Check For |
|---|---|
| Logic | Bugs, off-by-one errors, null handling |
| Security | Injection, XSS, secrets exposure, CORS |
| Performance | N+1 queries, unnecessary loops, missing indexes |
| Error handling | Unhandled exceptions, missing edge cases |
| Style | Consistency with surrounding code |
| Tests | New code covered? Edge cases tested? |
| API | Breaking changes to public interfaces? |
Provide: overall assessment (ship it / needs changes / major issues), specific issues with file:line references, suggested fixes.
Detect the framework and run tests:
| Config File | Framework | Command |
|---|---|---|
package.json (scripts.test) | npm/yarn/pnpm | npm test / pnpm test |
pytest.ini / pyproject.toml | pytest | pytest |
Cargo.toml | cargo | cargo test |
go.mod | go | go test ./... |
Makefile (test target) | make | make test |
On failure: parse output, identify the failing test, show the assertion, suggest a fix (don't auto-fix unless asked).
git log --oneline -10 for recent changesgit log and git diff against base branchgh pr view) - if so, show URL instead## Summary - 2-3 bullet points## Test plan - checklist of what was testedGather and present:
git status - working tree stategit log --oneline -5 - recent commitsgit branch -a - all branchesgit stash list - stashed changesgh pr list --state open - open PRsFor a given PR number: