neutronsg/neutron

Review a pull request or merge request against its Jira ticket, read-only, and report evidence-backed findings for a human approver. Use when asked to review a PR, MR, branch or diff before approval. Not for fixing code, posting comments or approving.

Before changing code for a Jira ticket, understand the part of the project it touches — who uses it, the business flow, the code and tests involved, open questions — and plan the ticket's starting branch and PR target. Use when starting on a project or picking up a new ticket. Read-only; not for implementing the change or answering general code questions.

Before a release is validated and deployed, check that the release branch holds exactly the tickets in the Jira Fix Version, and draft the release record — version, evidence, gaps, the tested artifact, and how every migration, configuration, schedule and external-call change is undone. Use when preparing a release, release candidate or patch release. Read-only; never deploys.

Release closeout after a release is merged back into main — inventory the repository's docs against the code, correct, add, merge, move or delete them, and open a docs-only PR with a file-by-file table, or record what was inspected when nothing needs changing. Run only when asked for release closeout by name. Never changes code; never merges.

Check a system against its SSAT (System Security Acceptance Test) checklist before go-live or a major release — decide which items apply, collect evidence for every line from the code, CI and deployed settings, and propose a status for each item (Closed, RA for risk acceptance, or NA). Use when preparing an SSAT, a security acceptance checklist or a go-live security review. Read-only; proposes, never accepts risk.