Back to skills
SkillHub ClubShip Full StackFull Stack

handler-work-tracker-github

Imported from https://github.com/fractary/claude-plugins.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars
4
Hot score
81
Updated
March 20, 2026
Overall rating
C3.1
Composite score
3.1
Best-practice grade
B80.4

Install command

npx @skill-hub/cli install fractary-claude-plugins-handler-work-tracker-github

Repository

fractary/claude-plugins

Skill path: plugins/work/skills/handler-work-tracker-github

Imported from https://github.com/fractary/claude-plugins.

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: fractary.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

  • Install handler-work-tracker-github into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
  • Review https://github.com/fractary/claude-plugins before adding handler-work-tracker-github to shared team environments
  • Use handler-work-tracker-github for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: handler-work-tracker-github
description: "[DEPRECATED] GitHub Issues handler - Use Fractary CLI instead"
model: haiku
handler_type: work-tracker
platform: github
deprecated: true
---

# GitHub Work Tracker Handler

> **⚠️ DEPRECATED**: This handler is deprecated. Skills now use Fractary CLI (`fractary work <command>`) directly instead of platform-specific handlers.
>
> **Migration**: See `specs/WORK-00356-implement-faber-cli-work-commands.md` for the CLI migration plan.

<CONTEXT>
You are the GitHub Issues handler for the work plugin. This handler is **DEPRECATED** as of the CLI migration.

**New approach**: Skills invoke `fractary work <command> --json` directly instead of routing through platform-specific handlers.

**Why deprecated**:
1. CLI provides platform abstraction at a lower level
2. Reduces context by eliminating handler layer
3. Simplifies skill implementations
4. Centralized maintenance in CLI codebase
</CONTEXT>

<CRITICAL_RULES>
1. **DEPRECATED** - Do not use this handler for new implementations
2. Skills should use Fractary CLI directly: `fractary work <command> --json`
3. Existing scripts retained for backward compatibility only
4. No new features will be added to this handler
</CRITICAL_RULES>

## Migration Guide

### Before (Handler-based)
```
Skill → Handler → scripts/*.sh → GitHub API
```

### After (CLI-based)
```
Skill → Fractary CLI → GitHub API
```

### Example Migration

**Before (deprecated):**
```bash
# Skill invokes handler script
./scripts/fetch-issue.sh 123
```

**After (recommended):**
```bash
# Skill invokes CLI directly
fractary work issue fetch 123 --json
```

## CLI Command Mapping

| Handler Operation | CLI Command | Status |
|-------------------|-------------|--------|
| fetch-issue | `fractary work issue fetch <n>` | ✅ Available |
| create-issue | `fractary work issue create` | ✅ Available |
| update-issue | `fractary work issue update <n>` | ✅ Available |
| close-issue | `fractary work issue close <n>` | ✅ Available |
| reopen-issue | `fractary work issue reopen <n>` | ❌ Missing |
| list-issues | `fractary work issue search` | ✅ Available |
| create-comment | `fractary work comment create <n>` | ✅ Available |
| list-comments | `fractary work comment list <n>` | ✅ Available |
| add-label | `fractary work label add <n>` | ✅ Available |
| remove-label | `fractary work label remove <n>` | ✅ Available |
| assign-issue | `fractary work issue assign <n>` | ❌ Missing |
| classify-issue | `fractary work issue classify <n>` | ❌ Missing |

## Backward Compatibility

Existing scripts in `scripts/` are retained for:
- Backward compatibility with old skill versions
- Reference implementations for CLI development
- Testing and validation

Scripts will be removed in a future major version once CLI migration is complete.

## Dependencies (for legacy scripts)

### Required Tools
- `gh` CLI (GitHub CLI) - https://cli.github.com
- `jq` - JSON processor
- `bash` 4.0+

### Environment Variables
- `GITHUB_TOKEN` - GitHub personal access token

## Script Locations (Legacy)

```
handler-work-tracker-github/
├── SKILL.md (this file)
├── scripts/                    # DEPRECATED - for backward compatibility only
│   ├── fetch-issue.sh
│   ├── classify-issue.sh
│   ├── create-comment.sh
│   ├── add-label.sh
│   ├── remove-label.sh
│   ├── close-issue.sh
│   ├── reopen-issue.sh
│   ├── update-state.sh
│   ├── list-issues.sh
│   └── ...
└── docs/
    └── github-api.md
```

## See Also

- `specs/WORK-00356-implement-faber-cli-work-commands.md` - CLI migration spec
- `specs/WORK-00356-1-missing-cli-work-commands.md` - Missing CLI commands
- `plugins/work/skills/cli-helper/SKILL.md` - CLI invocation patterns
handler-work-tracker-github | SkillHub