skills.rest
jay6697117
jay6697117COMMUNITY
Explore all skills by this author →
Website𝕏@nullGitHub

agency-jira-workflow-steward

Enforce Jira-linked Git workflows with traceable branches, commits, and PRs.

Updated Mar 22, 2026
Search Tags:#git#workflow#branching#traceability#jira#pull-request#auditable
One-click install
npx skills add https://github.com/jay6697117/agency-agents-antigravity --skill agency-jira-workflow-steward
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-jira-workflow-steward
Source: https://github.com/jay6697117/agency-agents-antigravity/tree/main/.agents/skills/agency-jira-workflow-steward
Command: npx skills add https://github.com/jay6697117/agency-agents-antigravity --skill agency-jira-workflow-steward

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps software delivery legible and auditable by enforcing Jira-linked Git workflows across teams, ensuring every change is traceable from Jira task to branch to commit to PR to release.

Core Features & Use Cases

  • Enforces Jira task linkage for branches, commits, and PR actions.
  • Preserves repository conventions while maintaining end-to-end traceability.
  • Prevents untracked or unconstrained work by blocking changes without an assigned Jira task.
  • Use Case: When delivering a new feature across multiple services, the agent ensures a single, Jira-backed narrative from issue to deployment.

Quick Start

Provide the Jira task ID and a concise change description to begin generating a traceable Git workflow.

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 linkage for Git branches and commits?▼

To enforce Jira task linkage, this workflow requires an explicit Jira task ID to generate branch names and commit messages, blocking unlinked changes until a valid reference is provided. It ensures end-to-end traceability from issue to deployment.

How do I map Git branches and pull requests to Jira tasks?▼

You map branches and pull requests to Jira tasks by providing the Jira task ID and a concise change description. The workflow generates traceable branch names and commit messages, maintaining a Jira-backed narrative across multi-repo projects.

Does this Jira-linked Git workflow support monorepo and multi-repo projects?▼

Yes, this Jira-linked Git workflow applies to both monorepo and multi-repo projects. It preserves repository conventions while enforcing Jira-backed traceability across feature work, bug fixes, hotfixes, and release preparation.

What happens if I make a commit without a Jira task ID?▼

If you commit without a Jira task ID, the workflow blocks the unlinked change. It enforces atomic commits using Gitmoji conventions and requires explicit Jira references to maintain an auditable delivery history.

When do I need to use a Jira-backed Git workflow for software delivery?▼

You need a Jira-backed Git workflow when delivering features across multiple services that require strict auditability. It ensures every change is traceable from Jira task to branch, commit, PR, and release.

Related Skills

Explore More Software Engineering Skills→
Likas07Likas07

jira-workflow-steward

Validate branch names, commit messages, and PRs against Jira task IDs.

Community
Advanced
Dev-Dennis-040Dev-Dennis-040
10

project-management-jira-workflow-steward

Generate Jira-linked Git workflows mapping tasks to branches, commits, PRs, and releases.

Community
Advanced
masa-codehubmasa-codehub

recording-changes

Stage changes and emit compliant git commit messages with branch validation.

Community
Intermediate
hivellmhivellm
15

rulebook-git-workflow

Enforce branch naming, conventional commits, and PR guidelines in Git workflows.

Official
Basic