Skills
.Work. You
Rest

mark-ticket-as-done

Community

Transition tickets to developer-done with full context.

Software Engineering#github#pull requests#jira#ticket workflow#projects v2#status transition#staged automation
Authormhert
Version1.0.0
Installs0

System Documentation

What problem does it solve?

It removes the manual, error-prone work of updating Jira workflow states or GitHub Projects v2 Status values after PRs are opened, while ensuring stakeholders get a clear comment that links every involved PR.

Core Features & Use Cases

  • Automated tracker transition: Moves a Jira ticket forward via workflow transition by name, or updates a GitHub issue’s Projects v2 Status field option by name.
  • Stakeholder-ready, exhaustive PR comment: Posts a markdown comment (converted to ADF for Jira) containing the ticket summary, affected features, verification steps, and a mandatory list of every PR involved.
  • Safety guardrails: Confirms the ticket, target status, PR links, and comment type, prevents replay on already-transitioned items, and validates project configuration (GitHub) before writing.

Quick Start

Run mark-ticket-as-done with the Jira key or GitHub issue identifier for the ticket whose PRs are already open, and provide or confirm the PR URLs and the target developer-done status name.

Dependency Matrix

Required Modules

ghaclimarklassianjqnode

Components

assets

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: mark-ticket-as-done
Download link: https://github.com/mhert/claude-code-helpers/archive/main.zip#mark-ticket-as-done

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.