Claude Skills by CoaseEdge

Explain deterministic architecture governance reports for repository changes without implementing architecture rules in the Agent adapter.

Use the preset-driven repo-governance CLI to adopt governance for an existing, new, or cloned repository. Use when a user asks to initialize governance, connect pre-push, select an explicit preset, or interpret bootstrap JSON before the first governed push.

Explain deterministic RG008 scope findings and task drift reports, and pause Agent work when the reported scope decision requires confirmation.

Recommend the governance tier for an executable test entry using repository evidence and RG002 JSON. Use when adding or moving tests, separating fixtures from executable entries, or reviewing provider, secret, device, production, cost, duration, or side-effect constraints.

Turn repo-governance PR/check JSON into concrete companion-test advice without claiming semantic coverage. Use for API, DTO, state, UI, interaction, command, build, or packaging changes and for RG001 test-evidence findings.

Review public command changes and their declared tests, documentation, and workflow consumers using RG004 JSON. Use when package scripts, build/test aliases, command semantics, environment assumptions, artifacts, or CI consumers change.

Gate repository-changing Agent work through the read-only repo-governance preflight JSON contract. Use before fixing bugs, adding features, editing code, running task tests, committing, or preparing a pull request, and when interpreting unmanaged, misconfigured, blocked, or disconnected-hook states.

Classify a CI failure from logs, repository evidence, and repo-governance JSON before proposing a fix. Use for failed tests, builds, workflows, provider checks, governance checks, stale assertions, stale automation, or suspected wrong CI tier.