菜单
Use this skill when the owner asks to inspect one repository for GDS context, manifest, policy, projection, Git-state, or agent-system drift. Produce read-only evidence and remediation options. Do not use it to fix, synchronize, commit, push, merge, release, or clean anything.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill only when the owner explicitly asks to install or verify GDS, its pinned bundle, and selected harness projections on a new macOS, Linux, server, or CI device. Build an exact reversible plan and keep secrets in approved stores. Do not use it to clone every estate repository or change global tools silently.
Use this skill only when the owner explicitly asks to apply one logical change across repositories selected by a GDS portfolio. Create independent repository subplans, canaries, bounded waves, and an aggregate journal. Do not use it for one repository or pretend the portfolio has one Git transaction.
Use this skill only when the owner explicitly asks to finish the current work completely across every affected Git repository: implement, verify, integrate, publish, update dependency pins, and remove only proven-safe completed branches or worktrees. Do not use it for status, routine sync, or unfinished handoff.
Use this skill only when the owner wants to preserve unfinished work for another device or session. Plan an exact checkpoint commit, push the task branch, and create or update a draft pull request when policy requires it. Do not use it to merge, complete, synchronize main, or clean branches and worktrees.
Use this skill only when the owner explicitly asks to create, inspect, synchronize, rehome, detach, freeze, archive, or otherwise change a fork lifecycle. Preserve fork-specific commits and upstream identity; force is never the default. Do not use it for ordinary source repositories or generic branch synchronization.
Use this skill only when the owner explicitly asks to add, replace, reclassify, or remove a module relationship for a project. Validate independent Git boundaries, typed relationships, .gitmodules or package metadata, visibility, and pin policy. Do not use it for ordinary code changes inside an existing module.
| name | gds-audit-repository |
| description | Use this skill when the owner asks to inspect one repository for GDS context, manifest, policy, projection, Git-state, or agent-system drift. Produce read-only evidence and remediation options. Do not use it to fix, synchronize, commit, push, merge, release, or clean anything. |
Audit one repository without changing local or external state.
gds context --json.gds status --json.gds validate repository --json.NOT_PROVEN evidence gaps.Stop before any repair, provider write, Git integration, or cleanup action.
Check that every finding names its object, evidence source, canonical owner, and safe next action.
Return confirmed findings first, followed by risks, evidence gaps, and a non-mutating remediation plan.
No additional runtime reference is required; use current structured gds output.