菜单
Generates a casual, human-sounding daily standup from git activity in the requested period, defaulting to the last workday. Use when the user says "standup", "daily standup", "write my standup", "what did I do yesterday", "write my daily update", or invokes /standup — even if they just ask "can you write my standup?"
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation.
Build and modify React Hook Form forms. Use when React Hook Form is mentioned, imported, installed, or established by project conventions, including controlled widget integration, schema validation, fetched edit forms, conditional fields, multi-step wizards, field arrays, submission errors, and dirty-state handling. Use the react-hook-form-audit skill when the job is review rather than implementation.
Capture a concrete work or learning receipt in today's Obsidian note, then optionally hand it to tweet-today or blog. Use when the user says "save this for sharing", "capture this receipt", "tweet this now", or when close-day promotes an Idea Worth Sharing.
End-of-day Obsidian ritual: close the active focus loop, triage Ideas Worth Sharing, and confirm tomorrow's carry-forward. Use for "close my day", "end of day", "wrap up today", or /close-day.
Daily startup ritual for the Obsidian vault: create today's workday note, surface exact context, and require the user to choose one daily outcome and next action. Use for "start my day", "daily startup", "today's focus", or /daily.
Obsidian goals review for quarterly, monthly, or weekly goal notes. Use when the user asks to review goals, run an OKR check-in, update goals, set monthly goals, check whether goals are on track, or runs /goals.
| name | standup |
| description | Generates a casual, human-sounding daily standup from git activity in the requested period, defaulting to the last workday. Use when the user says "standup", "daily standup", "write my standup", "what did I do yesterday", "write my daily update", or invokes /standup — even if they just ask "can you write my standup?" |
Transform git history into a human standup update. Nobody cares about commit messages — translate them into what you actually accomplished.
Completion criterion: git activity has been checked for the requested period (default: last workday), in the current repo or every repo the user names. If the evidence is insufficient, leave placeholders instead of inventing work.
Use the user-requested period when provided; otherwise use the last workday rather than blindly assuming the last 24 hours.
# Replace <since> / <until> with the requested period, or the last workday window.
git log --since="<since>" --until="<until>" --author="$(git config user.email)" --oneline
If multiple repos are relevant, run in each named repo. If no commits are found, skip to Step 3.
Done when the repo path(s), date window, and commit evidence are known or marked unavailable.
Map raw commit messages → casual language. The rule: write what you'd say out loud to a teammate, not what you typed in the terminal.
| Raw commit | Translated |
|---|---|
feat(modal): add purchase modal skeleton | Shipped the purchase modal skeleton |
fix: resolve pagination bug | Finally got that pagination bug squashed |
refactor: migrate to React Query | Got the React Query migration working |
chore: update dependencies | Bumped deps (skip — not worth a bullet) |
docs: update README | Updated the README (skip unless it's notable) |
Rules:
If no commits are found, do not invent work. Ask what they worked on, or return placeholders:
Yesterday I:
- [Fill in non-git work: meetings, planning, reviews, debugging, support]
Today I plan to:
- [Fill in today's focus]
Never mention the absence of commits in the standup body unless the user asks for evidence.
In order of preference:
git branch --show-current → parse intent
feat/payment-flow → "Continue the payment flow"fix/auth-timeout → "Fix the auth timeout issue"Yesterday I:
- [Accomplishment — active verb, specific]
- [Accomplishment 2]
Today I plan to:
- [Inferred from branch, asked, or placeholder]
Blockers:
- [Specific blocker only if mentioned]
Omit the Blockers section when there are no blockers or the user did not mention any.