skills.rest
anavvanzin
anavvanzinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agency-jira-workflow-steward

Enforce Jira-linked Git workflows across branches, commits, PRs, and releases.

Updated Apr 15, 2026
Search Tags:#traceability#jira#auditability#git-workflow#pull-request#branching-strategy#commit-hygiene
One-click install
npx skills add https://github.com/anavvanzin/Research --skill agency-jira-workflow-steward-anavvanzin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-jira-workflow-steward
Source: https://github.com/anavvanzin/Research/tree/main/cowork/integrations/antigravity/agency-jira-workflow-steward
Command: npx skills add https://github.com/anavvanzin/Research --skill agency-jira-workflow-steward-anavvanzin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tracks and enforces that every code change is traceable to a Jira task by requiring linkage from Jira to branch to commit to PR to release, preventing anonymous contributions.

Core Features & Use Cases

  • Enforces Jira-linked Git discipline across branches, commits, pull requests, and release gates.
  • Maintains clear ownership, audit trails, and change context across repositories (apps, infra, docs).
  • Works across multi-repo environments, enabling end-to-end traceability in complex delivery pipelines.

Quick Start

Require Jira task IDs for every branch, commit, and PR and configure the repository to reject anonymous changes.

Frequently Asked Questions about agency-jira-workflow-steward

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Jira task traceability in Git commits and pull requests?▼

Jira traceability in Git is enforced by requiring Jira task IDs in branch names, commit messages, and pull requests, and by configuring repositories to reject anonymous or unlinked merges to main.

What is a Jira-linked Git workflow and when do I need it?▼

A Jira-linked Git workflow connects Jira tasks to branches, commits, PRs, and releases. You need it to maintain clear ownership, audit trails, and change context across multi-repo delivery pipelines.

Can I use a Jira-linked branch strategy across infrastructure and documentation repositories?▼

Yes, this Jira-linked branch strategy applies across apps, infrastructure, and documentation repositories, guiding branch naming, commit hygiene, and release validation for multi-repo environments.

How do I block anonymous Git changes from merging into main?▼

To block anonymous Git changes, configure your repository to mandate pull requests for all merges to main and reject any commits or branches missing valid Jira task ID linkage.

What's the best way to maintain commit hygiene and auditability in multi-repo environments?▼

Maintaining commit hygiene in multi-repo environments requires enforcing a standard branch strategy, mandating pull requests, and validating that every commit and PR is traceable to a Jira task.

Related Skills

Explore More Software Engineering Skills→
CHNISamCHNISam

git-workflow

Automate Git commit message, branch naming, and merge strategy validation.

Community
Intermediate
yalehyaleh
21

CI/CD Optimization

Automate CI/CD pipelines with quality gates, release automation, and observability.

Community
Advanced
poitchpoitch

merge-pr

Squash-merge pull requests, delete remote and local branches, and pull main.

Community
Intermediate
YoshikemoloYoshikemolo
5

git-jira-integration

Generate Git branch names and validate commit messages against Jira issues.

Community
Intermediate