cgagentharness-project-guidance

Guides repository work by mapping tasks to authoritative CG-agent-harness source files and quality gates.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/cgfixit/CG-agent-harness --skill cgagentharness-project-guidance-cgfixit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cgagentharness-project-guidance
Source: https://github.com/cgfixit/CG-agent-harness/tree/main/.claude/skills/cgagentharness-project-guidance
Command: npx skills add https://github.com/cgfixit/CG-agent-harness --skill cgagentharness-project-guidance-cgfixit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents editing the CG-agent-harness repository can act on stale documentation or touch security-critical code without knowing the project's truth order, invariants, and quality bar. This Skill orients an agent before substantive repository work so changes follow the correct sources and gates. ## Core Features & Use Cases - Truth Order Enforcement: Establishes that code under src/ and assets/config.default.yaml outrank prose docs, and requires doc fixes in the same change set when behavior changes. - Task-to-Source Mapping: Tables map tasks (shim/I6, HTTP guards, write gates, clone jail, config, routes, packaging) to the exact files and tests to read first. - Skill Routing & Quality Bar: Directs which companion skill to load next (verify, invariant-guard, config-guard, release, etc.) and lists the mandatory checks: cargo fmt, clippy -D warnings, cargo test, and cargo deny check. - Use Case: Before modifying the write-gate path, an agent loads this Skill, reads src/agentic/writer.rs and the write-gate sections of INVARIANTS.md, then routes to the write-policy-redteam skill. ## Quick Start Ask the agent to load the cgagentharness-project-guidance skill before starting substantive work on the CG-agent-harness repository.

Frequently Asked Questions about cgagentharness-project-guidance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start working on the CG-agent-harness repository safely?▼

Load the project guidance skill first, then read the smallest current source set: code under src/, assets/config.default.yaml, INVARIANTS.md, AGENTS.md, and README.md. Code outranks prose when they disagree, and doc fixes belong in the same change set.

Which files should I read before changing write gates or the shim?▼

For shim or I6 work read src/shim, INVARIANTS.md I6, and tests/invariant_guard.rs. For write or publish path changes read src/agentic/writer.rs, the write-gate sections of INVARIANTS.md, and tests/real_repo_loop.rs.

What quality checks are required before submitting a harness change?▼

Run cargo fmt --all -- --check, cargo clippy --all-targets --all-features -- -D warnings, cargo test --all-targets with planner keys blanked, and cargo deny check. New routes need REGISTERED_PATHS updates and new shim actions need whitelist, CLI dispatch, and invariant updates together.

Does loading this skill grant permission to push or merge code?▼

No. The skill explicitly states it is not authorization to push, merge, release, or arm gates. It is repository guidance only, and any narrower operator authorization for the same task must be preserved.

When should I load a different skill instead of project guidance?▼

Project guidance is the entry point; it routes you onward. Use cgagentharness-verify for smoke/acceptance runs, invariant-guard before merging core-path security diffs, config-guard for config.default.yaml changes, and write-policy-redteam when hardening writer or clone jail code.