AGENTS.md · diff
git:20260725.26a9869 to git:20260726.0babf91
4 added, 18 removed. Audit A to A.
- # ForgeGuard Engineering Policy
-
- Use the ForgeGuard skills installed under `.codex/skills/` for every implementation task.
-
- Before changing code:
-
- 1. Inspect the repository, related implementations, tests, schemas, and conventions.
- 2. Select the engineering role that matches the affected area.
- 3. Search for existing reusable functions, services, hooks, and components.
- 4. Analyze input constraints, algorithmic complexity, database access, concurrency, and failure modes.
- 5. Define the smallest correct design and its verification strategy.
+ # ForgeGuard
- Before declaring completion:
+ Use the ForgeGuard engineering skill under `crates/forgeguard-core/assets/skills/engineering/` for every code change.
- 1. Run `forgeguard gate`.
- 2. Run the relevant formatter, linter, type checker, unit tests, integration tests, and build.
- 3. Review the complete diff for accidental or unrelated changes.
- 4. Report actual command results; never claim checks passed without executing them.
- 5. Disclose remaining risks and unverified assumptions.
+ Required cycle: inspect → design → implement → test → review → verify.
- Do not bypass ForgeGuard rules by disabling tests, linting, type checking, or security controls.
+ Inspect related code, callers, tests, contracts, and schemas first. Reuse proven behavior; avoid speculative global APIs/components. Analyze complexity, queries, concurrency, memory, and failure modes when relevant. Test changed behavior. Before completion, run `forgeguard gate --changed --output compact`, repository checks, and review full diff. Report evidence and remaining risk briefly. Never bypass quality or security controls.