メニュー
Use when applying the global Rust release-workflow pattern to the notfiles repo. Symptoms - you need the repo-specific release file, affected-crate exclusions, binary list, or GitHub-vs-Gitea cautions for notfiles.
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 | notfiles-release-workflow |
| description | Use when applying the global Rust release-workflow pattern to the notfiles repo. Symptoms - you need the repo-specific release file, affected-crate exclusions, binary list, or GitHub-vs-Gitea cautions for notfiles. |
Use this after rust-release-workflow-author when the target repo is notfiles. This skill only carries the repo-specific deltas that are not worth baking into the general Rust release skill.
.github/workflows/release.ymlnotfilesnothooksnotstrapnotgraphintegrationcargo fmt --all --checkcargo clippy --workspace --all-targets -- -D warningscargo nextest run --workspace# Read the repo workflows and package list
# Use Glob tool: glob '.github/**/*'
sed -n '1,260p' .github/workflows/ci.yml
sed -n '1,260p' .github/workflows/nightly.yml
cargo metadata --no-deps --format-version 1
rg -n '^version\s*=|^name\s*=' Cargo.toml crates/*/Cargo.toml
# Review the repo-specific release file after authoring
sed -n '1,320p' .github/workflows/release.yml
rust-release-workflow-author for the general workflow shape; keep this skill focused on notfiles specifics.integration package from release bumps.notcore and other shared workspace-crate changes as release-impacting for downstream consumers.main.| Symptom | Fix |
|---|---|
A release tries to bump the integration package | Filter test-only workspace members out of the affected crate set |
| GitHub release flow is authored against the wrong base branch | Check GitHub and Gitea main separately before finalizing the workflow |
| Asset packaging misses a CLI | Verify the workflow still packages notfiles, nothooks, notstrap, and notgraph |