handler-work-tracker-github

Manage GitHub issues and milestones via gh CLI with normalized JSON outputs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fractary/claude-plugins --skill handler-work-tracker-github
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handler-work-tracker-github
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/work/skills/handler-work-tracker-github
Command: npx skills add https://github.com/fractary/claude-plugins --skill handler-work-tracker-github

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill routes work-tracking tasks through GitHub Issues using gh CLI. It is deprecated in favor of direct CLI usage.

Core Features & Use Cases

  • Posts and updates issues, comments, and labels in GitHub.
  • Provides backward-compatible workflows for legacy projects.
  • Includes a migration pathway to Fractary CLI work commands.

Quick Start

Use this legacy handler only for existing workflows; prefer fractary work commands instead.

Frequently Asked Questions about handler-work-tracker-github

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

FAQPage Schema
How do I manage GitHub issues and milestones from the command line?▼

This Skill provides a CLI-driven handler that fetches issue details, creates and updates issues and milestones, manages labels and assignees, and posts comments—all through the gh CLI tool. It produces normalized JSON outputs for programmatic workflows.

Can I automate GitHub work tracking without leaving the terminal?▼

Yes, this handler routes work-tracking tasks through GitHub Issues using gh CLI, supporting issue creation, updates, labeling, assignee management, and linking—all driven from the command line with explicit error handling and exit codes.

What's the difference between using this handler and the fractary work commands?▼

This handler is deprecated in favor of direct fractary CLI work commands. It provides backward-compatible workflows for legacy projects but is intended as a migration pathway; new projects should use fractary work commands instead.

Does this work with existing GitHub repositories and configuration?▼

Yes, the handler loads repository configuration, integrates with your existing GitHub setup via gh CLI, and includes FABER metadata in communications for standardized work tracking across your projects.

Can I use this for legacy workflows while migrating to newer tools?▼

Yes, this handler is designed specifically for backward compatibility with legacy projects. It includes a migration pathway to Fractary CLI work commands, allowing gradual transition from existing workflows.