メニュー
Generate a smart commit message from staged or unstaged changes and create a commit. Use when the user wants to commit their work with a meaningful message.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Adopt Fable-class working discipline for this session — outcome-first communication, finish-the-turn autonomy, parallel tool use, faithful reporting. Use when the user says "/fable", "fable mode", "act like fable", or wants a smaller model (Opus, Sonnet) to work with the discipline of a Mythos-class model. Also invocable from other skills as a style preamble for long or high-stakes tasks.
Full workday recap across all tools — Jira, GitHub, Slack, Confluence, Google Docs, and Claude Code activity. Stores all data in SQLite with Turso sync for remote access. For Claude-only activity tracking, use /daily-review-v2 instead.
Claude Code activity tracking with SQLite/Turso storage — standup, weekly rollups, project reports, brag doc, friction tracking, goal tracking, heatmap, export. Data syncs to Turso for remote access. For full workday recap across all tools, use /daily-recap-v2 instead.
Transform a work-specific or company-specific skill/config into a generic, portable version. Replaces proprietary tools, internal URLs, and company references with generic equivalents while preserving the useful patterns and structure. Use when porting a work skill to the public config repo.
Sync ~/.claude/ global configs into this repo, sanitizing work-specific content (LinkedIn plugins, Captain MCP, work email, internal URLs). Use when the user wants to refresh this repo from their global Claude configs, pull in newly added skills/commands, or update sanitization rules. Two-pass flow with diff review before commit.
Deep discussion mode. No code changes, no file edits, no commands — pure thinking, exploration, and idea bouncing. Use when you want to explore a concept, design something, debate tradeoffs, or just think out loud. Claude will push back, ask questions, and present alternatives. Changes only happen if you explicitly say so.
| name | commit-changes |
| description | Generate a smart commit message from staged or unstaged changes and create a commit. Use when the user wants to commit their work with a meaningful message. |
Analyze current changes and generate a meaningful commit message following Conventional Commits specification.
Check for changes:
git status to see what files have changedStage files if needed:
git add -Agit add <files>Analyze staged changes:
git diff --cached --stat to see what's stagedgit diff --cached to see detailed changesShow diff preview to user:
git diff --cached to get the full staged diffGenerate commit message following Conventional Commits:
Format:
<type>(<scope>): <subject>
<body>
<footer>
Types:
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Formatting, missing semicolons, etc.refactor: Code change that neither fixes a bug nor adds a featureperf: Performance improvementtest: Adding or updating testschore: Maintenance tasks, dependency updatesci: CI/CD changesbuild: Build system changesGuidelines:
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> in footerPresent the commit message:
Suggested commit message:
feat(auth): add OAuth2 login support
Implement Google and GitHub OAuth2 providers for user authentication.
This replaces the legacy session-based auth system.
- Add OAuth2 configuration endpoints
- Implement token refresh logic
- Update user model with provider fields
Closes #123
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Ask for approval:
Create the commit:
git commit -m "$(cat <<'EOF'
<commit message here>
EOF
)"
Confirm success:
git log -1 --oneline to show the commit was created