The /release command serves as the strictly enforced Quality Gate before merging code into a production environment. It ensures that any version slated for release meets all technical, documentation, and roadmap criteria.
The 7-Step Quality Check
0. Rules Pre-flight (v1.5.4)
Before any check executes, the agent re-reads .agent/rules.md from disk to restore rule context. This is part of the Defense-in-Depth Layer 3 protection — ensuring rules survive context truncation in long sessions.
1. Linting & Formatting
Runs standard syntax and formatting checks (e.g., npm run lint). Guarantees clean and consistent code.
2. Test Suite
Executes the full array of Unit and Integration tests to ensure no logic regressions are introduced.
3. Build Verification
Verified that the application compiles or bundles successfully within a production-like environment.
4. Log Audit
Analyzes the sessions/ directory to ensure every relevant work session contributing to this release has been properly documented by the Agent.
5. Changelog Update
Verifies that CHANGELOG.md accurately reflects new features, performance improvements, or fixed bugs.
6. Version Bump
Automatically increments version indicators across critical files:
- Project contract (
project.md). - Manifest files (
package.json,VERSION). - Version badges in
README.md.
7. Milestone & Roadmap
Cross-references with targeted milestones in the plan. If the release satisfies a milestone, the system automatically marks it as shipped on the public Roadmap.
Relationships
/push— Push verified code to GitHub./verify— Verify individual tasks before inclusion in a release./end— Wrap up the final session before publication.