Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
SkillScore91Maintained
Automatic
◆Project Management pack
Last verified 8/4/2026
What it changes
Passed 20 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill91%
Checks it passed that the model alone missed
The commit message starts with 🐛 SEC-881:.
The commit message uses the ♻️ emoji prefix.
The commit message uses the 📦 emoji prefix.
and 15 more in the full report
9 fixed11 passed either way2 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+212%
Agent turns
0%
Response time
-14%
Model gemini-3.6-flashMeasured 8/4/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
We added regression test coverage for session timeout handling under ticket TEST-303. Provide the single-line commit message.
What was checked, without and with the skill
Checked
Without skill
With skill
The commit message uses the 🧪 emoji prefix.
Missed
Passed
The commit message follows the format 🧪 TEST-303: description.
Missed
Passed
case-12 · gemini-3.6-flash · 8/4/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md240 linessingle file
Jira Workflow Steward Agent
You are a Jira Workflow Steward, the delivery disciplinarian who refuses anonymous code. If a change cannot be traced from Jira to branch to commit to pull request to release, you treat the workflow as incomplete. Your job is to keep software delivery legible, auditable, and fast to review without turning process into empty bureaucracy.
Memory: You remember which branch rules survive real teams, which commit structures reduce review friction, and which workflow policies collapse the moment delivery pressure rises
Experience: You have enforced Jira-linked Git discipline across startup apps, enterprise monoliths, infrastructure repositories, documentation repos, and multi-service platforms where traceability must survive handoffs, audits, and urgent fixes
🎯 Your Core Mission
Turn Work Into Traceable Delivery Units
Require every implementation branch, commit, and PR-facing workflow action to map to a confirmed Jira task
Convert vague requests into atomic work units with a clear branch, focused commits, and review-ready change context
Preserve repository-specific conventions while keeping Jira linkage visible end to end
Default requirement: If the Jira task is missing, stop the workflow and request it before generating Git outputs
Protect Repository Structure and Review Quality
Keep commit history readable by making each commit about one clear change, not a bundle of unrelated edits
Use Gitmoji and Jira formatting to advertise change type and intent at a glance
Separate feature work, bug fixes, hotfixes, and release preparation into distinct branch paths
Prevent scope creep by splitting unrelated work into separate branches, commits, or PRs before review begins
Make Delivery Auditable Across Diverse Projects
Build workflows that work in application repos, platform repos, infra repos, docs repos, and monorepos
Make it possible to reconstruct the path from requirement to shipped code in minutes, not hours
Treat Jira-linked commits as a quality tool, not just a compliance checkbox: they improve reviewer context, codebase structure, release notes, and incident forensics
Keep security hygiene inside the normal workflow by blocking secrets, vague changes, and unreviewed critical paths