update-ticket-frontmatter

Update YAML frontmatter fields in ticket markdown files after implementation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill updates ticket YAML frontmatter fields (effort, commit_hash, category) automatically after a ticket's work has been implemented, ensuring consistent metadata tracking.

Core Features & Use Cases

  • Automatic frontmatter updates: Sets effort, commit_hash, and category based on the final commit and ticket status.
  • Post-implementation workflow: Integrates with your ticketing process to keep history accurate for audits and reporting.
  • Use Case: After implementing a feature, run this Skill to attach the committed hash and effort estimation to the ticket, and categorize it by outcome.

Quick Start

Use the update-ticket-frontmatter tool to modify a ticket's YAML frontmatter with a single command, e.g.: bash .claude/skills/update-ticket-frontmatter/sh/update.sh <ticket-path> <field> <value>

Frequently Asked Questions about update-ticket-frontmatter

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

FAQPage Schema
How do I automatically update YAML frontmatter in markdown files after a commit?

To automatically update YAML frontatter in markdown files, you can use a bash script with standard shell utilities to modify fields like effort, commit_hash, and category in place after implementation work is completed.

How do I insert or modify specific YAML fields in markdown frontmatter while enforcing field order?

To modify YAML fields in markdown frontmatter while enforcing field order, apply a shell utility script to individual ticket files that updates values and enforces the insertion order defined in the field rules.

What is the best way to track git commit hashes and effort estimations in ticket markdown files?

The best way to track git commit hashes and effort estimations in ticket markdown files is to run a post-implementation bash script that attaches the final committed hash and effort value directly to the ticket's YAML frontmatter.

Can I update ticket frontmatter fields in bulk across my entire repository?

This frontmatter update process is applied to individual ticket markdown files in your repository, meaning you target specific files rather than applying bulk updates across the entire repository at once.

Do I need any external dependencies to update markdown YAML frontmatter via bash?

You do not need external dependencies to update markdown YAML frontmatter via bash, as the process relies solely on standard shell utilities already available in your environment to modify files in place.

Why are my YAML frontmatter fields not staying in the correct order when updating ticket metadata?

YAML frontmatter fields may lose correct order when updating ticket metadata if the script does not enforce insertion order defined in field rules, which this shell utility specifically handles during in-place modification.