git:20260725.26a9869 to git:20260726.0babf91
4 added, 12 removed. Audit A to A.
- # ForgeGuard Engineering Policy
-
- Use the ForgeGuard skills installed under `.claude/skills/` whenever their scope matches the task.
+ # ForgeGuard
- Required workflow:
+ Use `/forgeguard-engineering` for every code change.
- 1. Inspect existing architecture, related code, tests, contracts, and database schema.
- 2. Choose the correct senior engineering role for the work.
- 3. Reuse the narrowest valid abstraction; do not create global APIs or components prematurely.
- 4. Analyze algorithmic complexity, query behavior, concurrency, memory, and external I/O.
- 5. Implement focused changes with relevant tests.
- 6. Run `forgeguard gate` and the repository's quality commands.
- 7. Review the final diff and report evidence, not assumptions.
+ Required cycle: inspect → design → implement → test → review → verify.
- Never claim an implementation is clean, optimal, secure, or production-ready without verification.
+ 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.