release-engineer

Run the preflight_check operation with the absolute path to your repository. It evaluates five gates — code health, documentation, metadata, security, and CI — and returns a verdict of READY, NOT_READY, or READY_WITH_WARNINGS along with blockers and warnings.

The ship operation scans git log since the last tag and categorizes commits into Added, Changed, Fixed, Removed, and Security sections. It then prepends a formatted entry for the new version to CHANGELOG.md automatically.

Yes, the ship operation supports pypi, npm, and crates as publish targets using build/twine, npm publish, or cargo publish. Publishing always pauses for explicit user confirmation because published packages are effectively permanent.

A test failure blocks the release with zero automatic retries. The agent reports which gate failed and why, and the release cannot proceed until tests pass or the user explicitly overrides the blocker.

Do not use it for auditing code quality or tech debt, debugging failing CI pipelines, or writing application code fixes. It also should not be used on repositories with no tests and no CI, since releasing untested code creates false readiness.

Yes, the portfolio_check operation runs preflight across all repositories in a directory and produces a shipping status matrix. It groups repos into shippable, almost ready, and not ready, and lists quick wins ordered by lowest effort first.