Ship rules say what must be true before a Jira work item ships: tests linked, reviewed by a person, rollback noted, security review for sign-in changes. You set them per project, by work type, label and component.
People attach evidence on the work item. Coding agents read the same rules and attach evidence through five tools on the Atlassian MCP server. Rules you mark "a person must confirm" stay open until a person confirms them in Jira, whatever an agent attaches.
The open-source skill file and an AGENTS.md snippet are at github.com/skillmerc/ship-rules-skill.
| Tool | What it does |
|---|---|
get-ship-readiness | The rules that apply to one work item, the evidence on each, whether it is ready, and the next steps. |
check-ready-to-ship | A short yes or no with the open rules and reasons. |
attach-ship-evidence | Attach a link or a note to one rule. Needs edit permission on the work item. |
list-blocked-work-items | Open work items of a project that are not ready, or only those blocked on one rule. |
get-ship-rules | Every rule of a project, or the rules for one work item. |
Built on Atlassian Forge. Everything stays in your Atlassian site. The app calls no outside service. Privacy policy. Terms of use.
Email kyle@skillmerc.com. Built by SKILLMERC (Pty) Ltd with an AI coding agent. Not affiliated with or endorsed by Atlassian.