菜单
Use when a repo is mirrored across GitHub and Gitea and you need to decide where to open or merge a PR. Symptoms - the branch tracks one forge, another forge has a different `main`, or GitHub tooling is available but the active branch lives on Gitea.
用 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 | dual-forge-pr-merge |
| description | Use when a repo is mirrored across GitHub and Gitea and you need to decide where to open or merge a PR. Symptoms - the branch tracks one forge, another forge has a different `main`, or GitHub tooling is available but the active branch lives on Gitea. |
Use this for repositories that exist on more than one forge. The point is to open and merge the PR where the branch and base actually live, not where the first CLI happens to work.
# Inspect remotes and branch tracking
git remote -v
git branch -vv
# Compare base branches across forges
git ls-remote github refs/heads/main
git ls-remote gitea refs/heads/main
# Check whether the current branch exists on each remote
branch=$(git branch --show-current)
git ls-remote github "refs/heads/$branch"
git ls-remote gitea "refs/heads/$branch"
main differs across remotes, do not treat them as interchangeable.gh or a forge-specific API.| Symptom | Fix |
|---|---|
| GitHub has no branch but Gitea does | Use Gitea for the PR or push the branch to GitHub first |
GitHub main is not the same commit as Gitea main | Pick the intended forge explicitly; do not merge blindly |
| CLI support exists for only one forge | Use read-only git checks first, then select the correct forge-specific path |