القائمة
Parse git history into structured changelogs. Use to generate release notes, audit commit conventions before tagging, or integrate with `godmode release` workflow.
التثبيت باستخدام 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.
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.
Triage and prioritize GitHub issues by type (bug/feature/chore), complexity (S/M/L), and priority (P1-P4). Detect duplicates, propose execution order, and generate task graphs for godmode automation.
| name | godmode:changelog |
| description | Parse git history into structured changelogs. Use to generate release notes, audit commit conventions before tagging, or integrate with `godmode release` workflow. |
| requires | [] |
| next | ["release-notes"] |
godmode release changelog subcommandCommits should follow the pattern:
<type>(<scope>): <description>
feat, fix, refactor, chore, docs, test, cigodmode-core,
godmode-cliExamples:
feat(godmode-core): add changelog generator
fix(godmode-cli): handle missing config file
refactor: unify error handling in dispatch module
docs: update CLI reference
test: add property tests for graph cycles
( or :)godmode-core): or after the typeProduce grouped markdown changelog:
# Changelog — <tag>..HEAD
## Features
### <crate>
- <commit description>
- <commit description>
## Fixes
### <crate>
- <commit description>
## Refactoring
...
## Other
...
## Non-Conventional Commits
- <full commit message> (reason: missing type, scope, or separator)
Omit sections with no entries. "Other" includes docs, test, chore, ci
and commits without a crate scope.
Write the generated changelog to CHANGELOG.md or .ctx/ manually and commit.
(godmode release changelog generates and prepends an entry from commits since the last
tag; this skill is for authoring richer notes and writing them with the Write tool.)
git loggit rebase outside godmode