jira-complete

Finalize Jira issues with code checks, Git pushes, status transitions, and verdict archiving.

3|1|Updated May 1, 2026
One-click install
npx skills add https://github.com/bigbulgogiburger/claude_jira_harness --skill jira-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-complete
Source: https://github.com/bigbulgogiburger/claude_jira_harness/tree/main/skills/jira-complete
Command: npx skills add https://github.com/bigbulgogiburger/claude_jira_harness --skill jira-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the Jira task completion process by performing final code quality checks, ensuring proper Git operations, updating Jira status, and archiving runtime verdicts automatically.

Core Features & Use Cases

  • Final Code Verification: Runs stack-specific linters, tests, and builds to ensure quality before closure.
  • Jira Status Automation: Transitions Jira issues to review or QA stages and posts structured completion comments.
  • Archiving and Reporting: Saves runtime verdicts and state snapshots into archive directories for traceability, updating central index.
  • Use Case: When development tasks are finished, use this Skill to validate, push, transition Jira tickets to QA, and preserve project verdicts effortlessly.

Quick Start

Execute "/jira-complete ISSUE-KEY" after final testing; the Skill will perform code checks, push changes, update Jira, and archive runtime data.

Frequently Asked Questions about jira-complete

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

FAQPage Schema
How do I automate Jira issue finalization with code quality checks and git push?

Automating Jira issue finalization involves running stack-specific linters and builds, pushing commits, transitioning issue status to QA, and archiving runtime verdicts. Use the issue key command after testing to trigger validation, push changes, and update Jira.

What is the process for transitioning Jira tickets to QA after development?

Transitioning Jira tickets to QA requires verifying code quality, updating project stages, and posting structured completion comments. This process ensures consistent workflow adherence and saves state snapshots into archive directories for traceability.

Can I run code verification and update Jira status across various tech stacks?

Yes, code verification and Jira status updates support various tech stacks. The process runs stack-specific linters, tests, and builds to ensure quality before closure, then transitions Jira issues to review stages.

How do I archive runtime verdicts and state snapshots for Jira issue traceability?

Archiving runtime verdicts involves saving runtime data and state snapshots into archive directories and updating a central index. This preserves project verdicts for traceability and ensures QA readiness after task completion.

What's the best way to ensure consistent development workflow adherence when closing Jira tasks?

Ensuring consistent development workflow adherence requires automating final code checks, Git operations, Jira status transitions, and runtime archiving. This eliminates manual steps and guarantees uniform process execution across projects.