メニュー
Use before cutting a release to verify tags, affected crates, gates, binaries, and target remote. Symptoms - you are about to tag a release, create a GitHub release, or automate publishing and want to catch the obvious failures before mutating history.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Audit godmode skills, agents, and plugin files for internal consistency, broken references, stale commands, and cross-skill contradictions. Use when asked to "introspect", "audit the skills", "review godmode", or after adding new skills.
Use at the start of every conversation to orient to available skills and workspace rules. Replaces superpowers entirely. Triggers on session start, "/godmode", or "what skills do you have".
Generate and maintain a `.ctx/godmode/memory-bank/` directory that captures project context backed by source code. The memory bank is injected into prompts via lifecycle hooks and updated incrementally as work progresses. Use when starting a new project, onboarding to an unfamiliar codebase, or when context drift is detected.
Patterns and techniques for adding governance, safety, and trust controls to AI agent systems in Rust. Use this skill when building agents that call external tools, implementing policy-based access controls, adding semantic intent classification to detect dangerous prompts, creating trust scoring systems for multi-agent workflows, building audit trails, or enforcing rate limits and content filters. Covers policy composition, tool wrappers, trust decay, and JSONL audit trails — all in Rust.
Parse git history into structured changelogs. Use to generate release notes, audit commit conventions before tagging, or integrate with `godmode release` workflow.
Dead code detector for Rust workspaces. Finds unused public API surface, orphaned test helpers, stale feature flags, and plugin artifacts referencing removed CLI subcommands. Cross-references pub exports against call sites across the workspace.
| name | release-readiness-check |
| description | Use before cutting a release to verify tags, affected crates, gates, binaries, and target remote. Symptoms - you are about to tag a release, create a GitHub release, or automate publishing and want to catch the obvious failures before mutating history. |
Use this right before a release commit, tag, or automated workflow run. It is a preflight that checks whether the repo is clean, the intended version is valid, the tag is unused, and the validation gates are green.
# Verify branch, worktree, and remotes
git status --short --branch
git remote -v
git branch -vv
# Check version/tag availability
git describe --tags --abbrev=0 --match 'v*'
git rev-parse "v<version>" 2>/dev/null || true
git ls-remote --tags <remote> "refs/tags/v<version>"
# Run release gates
cargo fmt --all --check
cargo clippy --workspace --all-targets -- -D warnings
cargo nextest run --workspace
| Symptom | Fix |
|---|---|
| Release fails because the tag already exists | Check local and remote tags before committing the bump |
| Release automation mutates the wrong branch | Verify current branch and remote tracking first |
| Last-minute clippy failure breaks the release | Run the full release gates before tagging |