mk:jira-dev — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited mk:jira-dev (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Forks to the jira-dev agent. Pure artifact generation — the user reviews and runs the resulting git/gh commands.
mk:ship may invoke bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh dev branch-name <KEY> during its branch-creation step (documentation-only — no automatic wiring exists today). Users opt in by passing the Jira key context to mk:ship.
../../agents/jira-dev.md../jira/references/{install-and-auth,cli-idioms,safety-framework}.mdreferences/branch-naming.md — convention reference (<type>/<KEY>-<slug>)references/smart-commits.md — smart-commit syntax for closing/transitioning from commit messagesreferences/commit-messages.md — Atlassian-aware commit-message conventionsmk:ship (consumes dev branch-name + dev pr-description), mk:jira-issue (issue must exist before branch creation), mk:jira-lifecycle (transitions via smart-commit footer)~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.