archive-ticket

Archive completed tickets, delegate commit creation, and update frontmatter.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/qmu/workaholic --skill archive-ticket
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive-ticket
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/archive-ticket
Command: npx skills add https://github.com/qmu/workaholic --skill archive-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commit, update-ticket-frontmatter.

What problem does it solve?

Archive ticket workflow - move ticket, delegate commit to commit skill, update frontmatter. This Skill automates the post-implementation workflow after a ticket is approved, ensuring consistent archiving, commit creation, and frontmatter synchronization.

Core Features & Use Cases

  • Ticket archiving: Move the completed ticket file into the archive folder on the current branch.
  • Commit delegation: Delegate commit message creation to the commit skill with standardized formatting.
  • Frontmatter synchronization: Update the archived ticket with the generated commit hash and category for traceability.

Quick Start

Run the archive script to archive a ticket: bash ~/.claude/plugins/marketplaces/workaholic/plugins/core/skills/archive-ticket/sh/archive.sh
<ticket-path> "<title>" <repo-url> "<motivation>" "<ux-change>" "<arch-change>" Follow the preloaded format-commit-message skill for message format.

Frequently Asked Questions about archive-ticket

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

FAQPage Schema
How do I automate moving a completed ticket to an archive folder and creating a git commit?

To automate ticket archiving and committing, you can run the archive script which moves the completed ticket file and delegates commit creation to a commit skill. This automates archiving, committing, and frontmatter updates.

How does ticket archiving synchronize frontmatter with the generated commit hash?

Ticket archiving delegates commit creation and then updates the archived ticket's frontmatter with the generated commit hash and category. This ensures traceability between the ticket and the actual git commit.

Do I need a valid effort value in frontmatter before archiving a ticket?

Yes, a valid effort value in the ticket's frontmatter is a strict prerequisite before archiving a ticket. The archive workflow enforces this requirement and will abort if the frontmatter update fails.

What happens if the frontmatter update fails during the ticket archive workflow?

If the frontmatter update fails during the ticket archiving process, the workflow will abort. This prevents inconsistent state by ensuring the archived ticket always has the correct commit traceability metadata.

Can I use a commit skill to delegate commit message creation when archiving tickets?

Yes, the archive ticket workflow delegates commit message creation to a commit skill with standardized formatting. You follow the preloaded format-commit-message skill for the message format.