メニュー
Generate and execute conventional commit messages by analyzing git diffs and conversation context. Use when creating git commits, generating commit messages, or documenting changes in conventional commit format.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | conventional-commits |
| description | Generate and execute conventional commit messages by analyzing git diffs and conversation context. Use when creating git commits, generating commit messages, or documenting changes in conventional commit format. |
Generate conventional commit messages by analyzing code changes and conversation context.
pnpm run format:fix before staging or committing. This uses the project's Prettier config from package.json.git status and git diff (or git diff --staged) to analyze changesgit log --oneline -10 to match the repository's commit style| Type | Use when |
|---|---|
feat | A new feature |
fix | A bug fix |
docs | Documentation only |
style | Formatting, whitespace (no logic change) |
refactor | Neither fixes a bug nor adds a feature |
perf | Performance improvement |
test | Adding or correcting tests |
build | Build system or external dependencies |
ci | CI configuration |
chore | Other changes (not src or test) |
revert | Reverts a previous commit |
Identify the affected area as a lowercase noun: component, module, or feature name (e.g., auth, api, i18n). Omit scope when the change spans multiple areas.
Format: <type>(<scope>): <subject>
Subject rules:
Body (optional, separate with blank line):
Closes #123, Refs #456Footer (optional):
BREAKING CHANGE: <description> or ! after type/scopeSee references/examples.md for concrete examples by type.
CRITICAL: Always run the project's format script before committing:
pnpm run format:fix
Then stage and commit:
git add <files> && git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body>
<footer>
EOF
)"
In sandboxed environments (Cursor IDE), request all permissions to preserve GPG signing. See references/sandbox-execution.md if commits fail.
pnpm run format:fix has been run (required)git status)git diff --staged)fix(auth): handle expired token refreshreferences/examples.md — Commit message examples by typereferences/sandbox-execution.md — GPG signing and Cursor sandbox troubleshootingMaintain AI proposal discovery and form preparation when adding or updating Agreements create routes. Use when adding a new proposal type, changing create form fields, or updating select-create-action / select-settings-action menus.
Scaffold an SDD ticket workspace when starting a new unit of work. Reads the developer config, classifies the task, picks the SDD level, and creates the ticket folder in hypha-context. Trigger when the developer says: 'I'm starting #X', 'let's begin <ticket>', 'new task', or 'starting work on X'. (To resume an in-progress ticket use hypha-task-resume. To wrap up use hypha-checkpoint.)
Read or update Hypha's GitHub issues, PRs, and project board (#14 "Hypha Platform — Active Work") via the gh CLI. Use when a technical developer (github.enabled in their config) says "update the board", "sync this to GitHub", "move
Read or update Hypha's GitHub issues, PRs, and project board (#14 "Hypha Platform — Active Work") via the gh CLI. Use when a technical developer (github.enabled in their config) says "update the board", "sync this to GitHub", "move
Draft a shareable summary of work — a daily update, a spec brief for the team, or a focused issue to run by the team. Three auto-detected modes: daily (recent work + next steps), spec (spec summary + acceptance criteria), issue (specific topic to raise). Writes to .hypha-context.local/briefs/ (local draft — developer decides what to share). Trigger when someone says: 'generate a brief', 'draft something to share', 'share my daily update', 'brief the team on this spec', 'I want to run this by the team', or 'create a brief for the team call'.
Surface an idea, observation, or proposal for team discussion without owning the improvement — creates a committed entry in the shared feedback/ folder in hypha-context. Two flavors: internal (engaged dev flagging something to discuss collectively) or external (any contributor providing input for engaged devs to act on). Trigger when someone says: 'flag this for the team', 'I have feedback on X', 'log this idea without a ticket', 'note this for discussion', 'I want to surface this but not own it'.