track-work

Validate GitHub PR closing keywords against issue acceptance criteria.

2|Updated Feb 23, 2026

Search Tags:#automation #workflow #pull request #github #issue tracking #backlog

Ready to run

npx skills add https://github.com/evanharmon1/harmon-devkit --skill track-work

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: track-work
Source: https://github.com/evanharmon1/harmon-devkit/tree/main/ai/skills/universal/track-work
Command: npx skills add https://github.com/evanharmon1/harmon-devkit --skill track-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill eliminates the common failure of stranded GitHub issues and orphaned follow-up work by enforcing strict, command-driven conventions for tracking, linking, and closing work items.

Core Features & Use Cases

Closing Keyword Guard: Prevents PRs from accidentally closing issues that still contain unfinished acceptance criteria.
Automated Issue Ticking: Safely updates issue acceptance criteria as you verify them during implementation.
Cross-Repo Tracking: Ensures follow-up work discovered in other repositories is filed immediately in the correct tracker with proper provenance.

Quick Start

Use the track-work skill to verify that your current PR does not prematurely close any issues by checking all closing keywords against the issue's remaining acceptance criteria.

Frequently Asked Questions about track-work

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

FAQPage Schema

How do I prevent a GitHub pull request from accidentally closing an issue with unfinished acceptance criteria?▼

Enforce strict closing keyword validation against issue acceptance criteria. Guard mechanisms intercept pull requests and block premature issue closures by verifying that all checklist items are completed before allowing status updates.

How do I automate acceptance criteria tracking across multiple GitHub repositories?▼

Automate acceptance criteria tracking by applying atomic status updates to linked issues across multiple repositories. Use GitHub CLI to verify completion status and safely update issue checklists as you validate them during implementation.

Do I need the GitHub CLI to manage issue lifecycles and cross-repository backlogs?▼

Yes, GitHub CLI is required. Local asset scripts use the CLI and jq to perform state verification and atomic status updates, ensuring accurate issue tracking and provenance for cross-repository development workflows.

What's the best way to track follow-up work discovered in a different GitHub repository?▼

Use cross-repo tracking to immediately file discovered follow-up work in the correct tracker. This enforces command-driven conventions that link items with proper provenance, eliminating stranded issues and orphaned backlog work.

Why does my GitHub issue remain open after a linked pull request is merged?▼

Issues remain open when strict validation blocks closing keywords due to unfinished acceptance criteria. The lifecycle management process verifies that all checklist items are complete before allowing state changes.

Can I use track-work to verify that a PR does not prematurely close any issues?▼

Yes, track-work verifies pull requests by checking all closing keywords against remaining acceptance criteria. It enforces strict command-driven conventions to prevent stranded GitHub issues and orphaned follow-up work.