Claude-skill-registry handler-work-tracker-jira

[DEPRECATED] Jira Cloud handler - Use Fractary CLI instead

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/handler-work-tracker-jira" ~/.claude/skills/majiayu000-claude-skill-registry-handler-work-tracker-jira && rm -rf "$T"

manifest: skills/data/handler-work-tracker-jira/SKILL.md

Jira 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 Jira Cloud 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:

CLI provides platform abstraction at a lower level
Reduces context by eliminating handler layer
Simplifies skill implementations
Centralized maintenance in CLI codebase </CONTEXT>

<CRITICAL_RULES>

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

Migration Guide

Before (Handler-based)

Skill → Handler → scripts/*.sh → Jira REST API

After (CLI-based)

Skill → Fractary CLI → Jira REST API

Example Migration

Before (deprecated):

# Skill invokes handler script
./scripts/fetch-issue.sh PROJ-123

After (recommended):

# Skill invokes CLI directly
fractary work issue fetch PROJ-123 --json

CLI Command Mapping

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

```
curl
```
- HTTP requests
```
jq
```
- JSON processor
```
base64
```
- Authentication encoding

Environment Variables

```
JIRA_URL
```
- Jira instance URL (https://company.atlassian.net)
```
JIRA_EMAIL
```
- User email for authentication
```
JIRA_TOKEN
```
- API token
```
JIRA_PROJECT_KEY
```
- Default project key (e.g., PROJ)

Script Locations (Legacy)

handler-work-tracker-jira/
├── 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/
    └── jira-api.md

Jira-Specific Notes (Reference)

Authentication

Jira uses Basic Auth with email + API token.

Issue Keys

Format:

PROJECT-NUMBER

(e.g., PROJ-123)

Text Format

Jira uses Atlassian Document Format (ADF) for rich text.

Workflow Transitions

State changes require workflow transitions, not direct status updates.