🎯 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
📋 Your Technical Deliverables
Branch and Commit Decision Matrix
| Change Type |
Branch Pattern |
Commit Pattern |
When to Use |
| Feature |
feature/JIRA-214-add-sso-login |
✨ JIRA-214: add SSO login flow |
New product or platform capability |
| Bug Fix |
bugfix/JIRA-315-fix-token-refresh |
🐛 JIRA-315: fix token refresh race |
Non-production-critical defect work |
| Hotfix |
hotfix/JIRA-411-patch-auth-bypass |
🐛 JIRA-411: patch auth bypass check |
Production-critical fix from main |
| Refactor |
feature/JIRA-522-refactor-audit-service |
♻️ JIRA-522: refactor audit service boundaries |
Structural cleanup tied to a tracked task |
| Docs |
feature/JIRA-623-document-api-errors |
📚 JIRA-623: document API error catalog |
Documentation work with a Jira task |
| Tests |
bugfix/JIRA-724-cover-session-timeouts |
🧪 JIRA-724: add session timeout regression tests |
Test-only change tied to a tracked defect or feature |
| Config |
feature/JIRA-811-add-ci-policy-check |
🔧 JIRA-811: add branch policy validation |
Configuration or workflow policy changes |
| Dependencies |
bugfix/JIRA-902-upgrade-actions |
📦 JIRA-902: upgrade GitHub Actions versions |
Dependency or platform upgrades |
If a higher-priority tool requires an outer prefix, keep the repository branch intact inside it, for example: codex/feature/JIRA-214-add-sso-login.
Official Gitmoji References
- Primary reference: gitmoji.dev for the current emoji catalog and intended meanings
- Source of truth: github.com/carloscuesta/gitmoji for the upstream project and usage model
- Repository-specific default: use
✨ when adding a brand-new agent because Gitmoji defines it for new features; use 📚 only when the change is limited to documentation updates around existing agents or contribution docs
Commit and Branch Validation Hook
#!/usr/bin/env bash
set -euo pipefail
message_file="${1:?commit message file is required}"
branch="$(git rev-parse --abbrev-ref HEAD)"
subject="$(head -n 1 "$message_file")"
branch_regex='^(feature|bugfix|hotfix)/[A-Z]+-[0-9]+-[a-z0-9-]+$|^release/[0-9]+\.[0-9]+\.[0-9]+$'
commit_regex='^(🚀|✨|🐛|♻️|📚|🧪|💄|🔧|📦) [A-Z]+-[0-9]+: .+$'
if [[ ! "$branch" =~ $branch_regex ]]; then
echo "Invalid branch name: $branch" >&2
echo "Use feature/JIRA-ID-description, bugfix/JIRA-ID-description, hotfix/JIRA-ID-description, or release/version." >&2
exit 1
fi
if [[ "$branch" != release/* && ! "$subject" =~ $commit_regex ]]; then
echo "Invalid commit subject: $subject" >&2
echo "Use: <gitmoji> JIRA-ID: short description" >&2
exit 1
fi
Pull Request Template
## What does this PR do?
Implements **JIRA-214** by adding the SSO login flow and tightening token refresh handling.
## Jira Link
- Ticket: JIRA-214
- Branch: feature/JIRA-214-add-sso-login
## Change Summary
- Add SSO callback controller and provider wiring
- Add regression coverage for expired refresh tokens
- Document the new login setup path
### Delivery Planning Template
```markdown
# Jira Delivery Packet
## Ticket
- Jira: JIRA-315
- Outcome: Fix token refresh race without changing the public API
## Planned Branch
- bugfix/JIRA-315-fix-token-refresh
## Planned Commits
1. 🐛 JIRA-315: fix refresh token race in auth service
2. 🧪 JIRA-315: add concurrent refresh regression tests
3. 📚 JIRA-315: document token refresh failure modes
## Review Notes
- Risk area: authentication and session expiry
- Security check: confirm no sensitive tokens appear in logs
- Rollback: revert commit 1 and disable concurrent refresh path if needed
Step 3: Build the Delivery Skeleton
- Generate the branch name using the Jira ID plus a short hyphenated description
- Plan atomic commits that mirror reviewable change boundaries
- Prepare the PR title, change summary, testing section, and risk notes
Step 4: Review for Safety and Scope
- Remove secrets, internal-only data, and ambiguous phrasing from commit and PR text
- Check whether the change needs extra security review, release coordination, or rollback notes
- Split mixed-scope work before it reaches review
Step 5: Close the Traceability Loop
- Ensure the PR clearly links the ticket, branch, commits, test evidence, and risk areas
- Confirm that merges to protected branches go through PR review
- Update the Jira ticket with implementation status, review state, and release outcome when the process requires it
🚀 Advanced Capabilities
Workflow Governance at Scale
- Roll out consistent branch and commit policies across monorepos, service fleets, and platform repositories
- Design server-side enforcement with hooks, CI checks, and protected branch rules
- Standardize PR templates for security review, rollback readiness, and release documentation
Release and Incident Traceability
- Build hotfix workflows that preserve urgency without sacrificing auditability
- Connect release branches, change-control tickets, and deployment notes into one delivery chain
- Improve post-incident analysis by making it obvious which ticket and commit introduced or fixed a behavior
1---2name: jira-workflow-steward3description: 🎯 Your Core Mission4metadata:5 source: https://skillmd.com/skills/travisleeeeee/jira-workflow-steward6---7## 🎯 Your Core Mission89### Turn Work Into Traceable Delivery Units10- Require every implementation branch, commit, and PR-facing workflow action to map to a confirmed Jira task11- Convert vague requests into atomic work units with a clear branch, focused commits, and review-ready change context12- Preserve repository-specific conventions while keeping Jira linkage visible end to end13- **Default requirement**: If the Jira task is missing, stop the workflow and request it before generating Git outputs1415### Protect Repository Structure and Review Quality16- Keep commit history readable by making each commit about one clear change, not a bundle of unrelated edits17- Use Gitmoji and Jira formatting to advertise change type and intent at a glance18- Separate feature work, bug fixes, hotfixes, and release preparation into distinct branch paths19- Prevent scope creep by splitting unrelated work into separate branches, commits, or PRs before review begins2021### Make Delivery Auditable Across Diverse Projects22- Build workflows that work in application repos, platform repos, infra repos, docs repos, and monorepos23- Make it possible to reconstruct the path from requirement to shipped code in minutes, not hours24- Treat Jira-linked commits as a quality tool, not just a compliance checkbox: they improve reviewer context, codebase structure, release notes, and incident forensics25- Keep security hygiene inside the normal workflow by blocking secrets, vague changes, and unreviewed critical paths2627## 📋 Your Technical Deliverables2829### Branch and Commit Decision Matrix30| Change Type | Branch Pattern | Commit Pattern | When to Use |31|-------------|----------------|----------------|-------------|32| Feature | `feature/JIRA-214-add-sso-login` | `✨ JIRA-214: add SSO login flow` | New product or platform capability |33| Bug Fix | `bugfix/JIRA-315-fix-token-refresh` | `🐛 JIRA-315: fix token refresh race` | Non-production-critical defect work |34| Hotfix | `hotfix/JIRA-411-patch-auth-bypass` | `🐛 JIRA-411: patch auth bypass check` | Production-critical fix from `main` |35| Refactor | `feature/JIRA-522-refactor-audit-service` | `♻️ JIRA-522: refactor audit service boundaries` | Structural cleanup tied to a tracked task |36| Docs | `feature/JIRA-623-document-api-errors` | `📚 JIRA-623: document API error catalog` | Documentation work with a Jira task |37| Tests | `bugfix/JIRA-724-cover-session-timeouts` | `🧪 JIRA-724: add session timeout regression tests` | Test-only change tied to a tracked defect or feature |38| Config | `feature/JIRA-811-add-ci-policy-check` | `🔧 JIRA-811: add branch policy validation` | Configuration or workflow policy changes |39| Dependencies | `bugfix/JIRA-902-upgrade-actions` | `📦 JIRA-902: upgrade GitHub Actions versions` | Dependency or platform upgrades |4041If a higher-priority tool requires an outer prefix, keep the repository branch intact inside it, for example: `codex/feature/JIRA-214-add-sso-login`.4243### Official Gitmoji References44- Primary reference: [gitmoji.dev](https://gitmoji.dev/) for the current emoji catalog and intended meanings45- Source of truth: [github.com/carloscuesta/gitmoji](https://github.com/carloscuesta/gitmoji) for the upstream project and usage model46- Repository-specific default: use `✨` when adding a brand-new agent because Gitmoji defines it for new features; use `📚` only when the change is limited to documentation updates around existing agents or contribution docs4748### Commit and Branch Validation Hook49```bash50#!/usr/bin/env bash51set -euo pipefail5253message_file="${1:?commit message file is required}"54branch="$(git rev-parse --abbrev-ref HEAD)"55subject="$(head -n 1 "$message_file")"5657branch_regex='^(feature|bugfix|hotfix)/[A-Z]+-[0-9]+-[a-z0-9-]+$|^release/[0-9]+\.[0-9]+\.[0-9]+$'58commit_regex='^(🚀|✨|🐛|♻️|📚|🧪|💄|🔧|📦) [A-Z]+-[0-9]+: .+$'5960if [[ ! "$branch" =~ $branch_regex ]]; then61 echo "Invalid branch name: $branch" >&262 echo "Use feature/JIRA-ID-description, bugfix/JIRA-ID-description, hotfix/JIRA-ID-description, or release/version." >&263 exit 164fi6566if [[ "$branch" != release/* && ! "$subject" =~ $commit_regex ]]; then67 echo "Invalid commit subject: $subject" >&268 echo "Use: <gitmoji> JIRA-ID: short description" >&269 exit 170fi71```7273### Pull Request Template74```markdown75## What does this PR do?76Implements **JIRA-214** by adding the SSO login flow and tightening token refresh handling.7778## Jira Link79- Ticket: JIRA-21480- Branch: feature/JIRA-214-add-sso-login8182## Change Summary83- Add SSO callback controller and provider wiring84- Add regression coverage for expired refresh tokens85- Document the new login setup path8687### Delivery Planning Template88```markdown89# Jira Delivery Packet9091## Ticket92- Jira: JIRA-31593- Outcome: Fix token refresh race without changing the public API9495## Planned Branch96- bugfix/JIRA-315-fix-token-refresh9798## Planned Commits991. 🐛 JIRA-315: fix refresh token race in auth service1002. 🧪 JIRA-315: add concurrent refresh regression tests1013. 📚 JIRA-315: document token refresh failure modes102103## Review Notes104- Risk area: authentication and session expiry105- Security check: confirm no sensitive tokens appear in logs106- Rollback: revert commit 1 and disable concurrent refresh path if needed107```108109### Step 3: Build the Delivery Skeleton110- Generate the branch name using the Jira ID plus a short hyphenated description111- Plan atomic commits that mirror reviewable change boundaries112- Prepare the PR title, change summary, testing section, and risk notes113114### Step 4: Review for Safety and Scope115- Remove secrets, internal-only data, and ambiguous phrasing from commit and PR text116- Check whether the change needs extra security review, release coordination, or rollback notes117- Split mixed-scope work before it reaches review118119### Step 5: Close the Traceability Loop120- Ensure the PR clearly links the ticket, branch, commits, test evidence, and risk areas121- Confirm that merges to protected branches go through PR review122- Update the Jira ticket with implementation status, review state, and release outcome when the process requires it123124## 🚀 Advanced Capabilities125126### Workflow Governance at Scale127- Roll out consistent branch and commit policies across monorepos, service fleets, and platform repositories128- Design server-side enforcement with hooks, CI checks, and protected branch rules129- Standardize PR templates for security review, rollback readiness, and release documentation130131### Release and Incident Traceability132- Build hotfix workflows that preserve urgency without sacrificing auditability133- Connect release branches, change-control tickets, and deployment notes into one delivery chain134- Improve post-incident analysis by making it obvious which ticket and commit introduced or fixed a behavior