메뉴
Analyzes recent commits to surface unique coding patterns and adds them to CLAUDE.md or skills. Use when asked to update CLAUDE.md, extract patterns from commits, or "learn from my code". Also use when the user says "what patterns do I follow" or "update my preferences".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Reviews the current branch diff for bugs, edge cases, performance regressions, and behavior interactions. Use when asked for a code review, "review my changes", "check this code", or "anything wrong with this". This is a quick, focused review — for comprehensive multi-agent reviews, use full-code-review instead.
Analyzes code against staff-engineer patterns (security, architecture, simplicity, completeness, hygiene). Use when asked for a staff or senior code review, "staff review", "pattern review", or "review this like a staff engineer". This is the most thorough single-agent review — for multi-agent reviews, use full-code-review.
Generate monthly client progress reports for RailsPilot. Uses gh CLI to list the user's merged PRs, applies feature sizing rules, and drafts a numbered-list email. Use when asked for a monthly progress report, client delivery summary, or "progress report for [Month]".
Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
Write a warm, human-to-human written response (handoffs, status updates, testing notes for QA, sign-off requests, confirming assumptions before merging, or escalating an open question). Use when the user asks to draft a response, reply to a thread, write a handoff, send testing notes, ask the team to confirm something, phrase a Slack or PR comment, or convert dev-flavored notes into a message a teammate would actually enjoy reading.
Trim editorial bloat from technical docs (integration writeups, ADRs, investigation notes, READMEs). Proposes a unified diff with per-cut rationale and waits for approval. Use when asked to "trim this doc", "tighten this writeup", "filter pass on X.md", "prune the doc", or "cut the slop from this writeup".
| name | update-CLAUDE |
| description | Analyzes recent commits to surface unique coding patterns and adds them to CLAUDE.md or skills. Use when asked to update CLAUDE.md, extract patterns from commits, or "learn from my code". Also use when the user says "what patterns do I follow" or "update my preferences". |
Analyze recent commits to discover coding patterns worth codifying in CLAUDE.md or existing skills, so future sessions follow the same conventions automatically.
Read current CLAUDE.md to understand what's already documented.
Examine recent commits — run git log --oneline -10 to see subjects, then
git show <sha> for each to read the actual diffs. Focus on the user's commits
(match against git config user.email), not bot or CI commits.
Identify patterns — look for recurring choices that reflect intentional preferences, not one-off decisions. Good candidates:
#call on service objects)Filter against what's already in CLAUDE.md — only surface patterns that aren't already documented. Skip anything that's just standard Rails convention unless the user deviates from it in a consistent, intentional way.
Present findings — show each candidate pattern with a code example from the commits. Ask the user which ones to add.
Apply approved patterns — add to CLAUDE.md under the appropriate section, or update a relevant skill if the pattern is skill-specific (e.g., a testing pattern goes in rspec-testing, not CLAUDE.md).