メニュー
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/patrickking67/godmode --skill covenantコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
| name | covenant |
| description | Craft and create a Conventional Commit from your current changes. |
Turn the current changes into one clean, well-described commit. Running this command IS the user's explicit request to create a commit; proceed without asking again.
Run these in parallel to understand what changed and how this repo writes commits:
git status: what is staged, unstaged, and untracked.git diff and git diff --staged: the actual content of the changes.git log: recent messages, so you match the repo's existing style and prefixes.Read enough of the diff to understand the intent, not just the surface edits.
Decide what belongs in this commit. Group related edits together. If the changes are clearly unrelated (say, a bug fix plus an unrelated refactor), recommend splitting them into separate commits and propose how, rather than bundling everything into one.
Write a Conventional Commit: type(scope): subject.
feat, fix, chore, docs, refactor, test (match repo usage).Author the commit ONLY as the user's configured git identity. NEVER add a co-author,
Co-Authored-By, Signed-off-by, a "Generated with" or "Created by" line, or any
AI, assistant, or bot attribution or trailer of any kind.
Add the relevant files by name. Avoid git add -A and git add .; they sweep in
noise and secrets. Never stage .env, credential files, keys, or other secrets; if the
user explicitly asks to commit such a file, warn them clearly before doing so.
Pass the message via a heredoc so formatting stays clean:
git commit -F - <<'EOF'
fix(auth): reject expired tokens before refresh
Refresh path skipped the expiry check, letting stale tokens through.
EOF
Create a NEW commit. Never use --amend unless the user explicitly asks. Never push.
Never use --no-verify or otherwise skip hooks; if a pre-commit hook fails, fix the
underlying issue, re-stage, and make a new commit rather than bypassing it.
Run git status and git log -1 to show the result. Report the commit subject and
which files landed in one tight summary.