Agent skill

Issue Manage

by catlog22 in catlog22/Claude-Code-Workflow

Interactive issue management with menu-driven CRUD operations.

MITAuto-check: notes

Install Issue Manage

skills CLI
$ npx skills add catlog22/Claude-Code-Workflow --skill issue-manage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install catlog22/Claude-Code-Workflow issue-manage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/issue-manage .claude/skills/issue-manage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
issue-manage
GitHub stars
2.1k
Token cost
~2.1k tokens
SKILL.md length
350 words
Files
1
Skills in repo
82
Repo updated
First seen
Licence
MIT

At a glance

Interactive issue management with menu-driven CRUD operations.

  • Works in 6 steps: LIST 📋 → VIEW 🔍 → EDIT ✏️ → …
  • Managing issues
  • SKILL.md covers Quick Start, CLI Endpoints, Operations and Workflow, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Issue Manage is an agent skill from catlog22/Claude-Code-Workflow. Interactive issue management with menu-driven CRUD operations. Use when managing issues, viewing issue status, editing issue fields, performing bulk operations, or viewing issue history. Triggers on "manage issue", "list issues", "edit issue", "delete issue", "bulk update", "issue dashboard", "issue history", "completed issues".

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: JSON-driven multi-agent cadence-team development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. The licence is MIT.

When your agent uses it

  • Managing issues
  • Viewing issue status
  • Editing issue fields
  • Performing bulk operations

Example prompts

  • “manage issue”
  • “list issues”
  • “edit issue”
  • “/issue-manage”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Write, AskUserQuestion, Agent, Glob

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. LIST 📋
  2. VIEW 🔍
  3. EDIT ✏️
  4. DELETE 🗑️
  5. HISTORY 📚
  6. BULK 📦

What it can do on your machine

Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • AskUserQuestion
    • Agent
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript and bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Issue Manage loads about 2.1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 350 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, AskUserQuestion, Agent, Glob

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 350 words, ~2,075 tokens.

Download SKILL.mdSave it as .claude/skills/issue-manage/SKILL.md (or your agent's skills folder).
name
issue-manage
description
Interactive issue management with menu-driven CRUD operations. Use when managing issues, viewing issue status, editing issue fields, performing bulk operations, or viewing issue history. Triggers on "manage issue", "list issues", "edit issue", "delete issue", "bulk update", "issue dashboard", "issue history", "completed issues".
allowed-tools
Bash, Read, Write, AskUserQuestion, Agent, Glob

Issue Management Skill

Interactive menu-driven interface for issue CRUD operations via ccw issue CLI.

Quick Start

Ask me:

  • "Show all issues" → List with filters
  • "View issue GH-123" → Detailed inspection
  • "Edit issue priority" → Modify fields
  • "Delete old issues" → Remove with confirmation
  • "Bulk update status" → Batch operations
  • "Show completed issues" → View issue history
  • "Archive old issues" → Move to history

CLI Endpoints

bash
# Core operations
ccw issue list                      # List active issues
ccw issue list <id> --json          # Get issue details
ccw issue history                   # List completed issues (from history)
ccw issue history --json            # Completed issues as JSON
ccw issue status <id>               # Detailed status
ccw issue init <id> --title "..."   # Create issue
ccw issue task <id> --title "..."   # Add task
ccw issue bind <id> <solution-id>   # Bind solution
ccw issue update <id> --status completed  # Complete & auto-archive

# Solution queries
ccw issue solution <id>             # List solutions for a single issue
ccw issue solution <id> --brief     # Brief: solution_id, files_touched, task_count
ccw issue solutions                 # Batch list all bound solutions
ccw issue solutions --status planned --brief  # Filter by issue status

# Queue management
ccw issue queue                     # List current queue
ccw issue queue add <id>            # Add to queue
ccw issue queue list                # Queue history
ccw issue queue switch <queue-id>   # Switch queue
ccw issue queue archive             # Archive queue
ccw issue queue delete <queue-id>   # Delete queue
ccw issue next                      # Get next task
ccw issue done <queue-id>           # Mark completed
ccw issue update --from-queue       # Sync statuses from queue

Operations

1. LIST 📋

Filter and browse issues:

┌─ Filter by Status ─────────────────┐
│ □ All        □ Registered          │
│ □ Planned    □ Queued              │
│ □ Executing  □ Completed           │
└────────────────────────────────────┘

Flow:

  1. Ask filter preferences → ccw issue list --json
  2. Display table: ID | Status | Priority | Title
  3. Select issue for detail view
2. VIEW 🔍

Detailed issue inspection:

┌─ Issue: GH-123 ─────────────────────┐
│ Title: Fix authentication bug       │
│ Status: planned | Priority: P2      │
│ Solutions: 2 (1 bound)              │
│ Tasks: 5 pending                    │
└─────────────────────────────────────┘

Flow:

  1. Fetch ccw issue status <id> --json
  2. Display issue + solutions + tasks
  3. Offer actions: Edit | Plan | Queue | Delete
3. EDIT ✏️

Modify issue fields:

FieldOptions
TitleFree text
PriorityP1-P5
Statusregistered → completed
ContextProblem description
LabelsComma-separated

Flow:

  1. Select field to edit
  2. Show current value
  3. Collect new value via AskUserQuestion
  4. Update .workflow/issues/issues.jsonl
4. DELETE 🗑️

Remove with confirmation:

⚠️ Delete issue GH-123?
This will also remove:
- Associated solutions
- Queued tasks

[Delete] [Cancel]

Flow:

  1. Confirm deletion via AskUserQuestion
  2. Remove from issues.jsonl
  3. Clean up solutions/<id>.jsonl
  4. Remove from queue.json
5. HISTORY 📚

View and manage completed issues:

┌─ Issue History ─────────────────────┐
│ ID                 Completed   Title │
│ ISS-001  2025-12-28 12:00   Fix bug │
│ ISS-002  2025-12-27 15:30   Feature │
└──────────────────────────────────────┘

Flow:

  1. Fetch ccw issue history --json
  2. Display table: ID | Completed At | Title
  3. Optional: Filter by date range

Auto-Archive: When issue status → completed:

  • Issue moves from issues.jsonl → issue-history.jsonl
  • Solutions remain in solutions/<id>.jsonl
  • Queue items marked completed
Show full SKILL.md (130 more words)Show less
6. BULK 📦

Batch operations:

OperationDescription
Update StatusChange multiple issues
Update PriorityBatch priority change
Add LabelsTag multiple issues
Delete MultipleBulk removal
Queue All PlannedAdd all planned to queue
Retry All FailedReset failed tasks
Sync from QueueUpdate statuses from active queue

Workflow

┌────────────────────────────────────────────────┐
│              Main Menu                          │
│  ┌────┐ ┌────┐ ┌────┐ ┌─────┐ ┌────┐          │
│  │List│ │View│ │Edit│ │Hist.│ │Bulk│          │
│  └──┬─┘ └──┬─┘ └──┬─┘ └──┬──┘ └──┬─┘          │
└─────┼──────┼──────┼──────┼───────┼─────────────┘
      │      │      │      │       │
      ▼      ▼      ▼      ▼       ▼
   Filter  Detail  Fields  History Multi
   Select  Actions Update  Browse  Select
      │      │      │      │       │
      └──────┴──────┴──────┴───────┘
                    │
                    ▼
             Back to Menu

Issue Lifecycle:

registered → planned → queued → executing → completed
                                               │
                                               ▼
                                    issue-history.jsonl

Implementation Guide

Entry Point
javascript
// Parse input for issue ID
const issueId = input.match(/^([A-Z]+-\d+|ISS-\d+)/i)?.[1];

// Show main menu
await showMainMenu(issueId);
Main Menu Pattern
javascript
// 1. Fetch dashboard data
const issues = JSON.parse(Bash('ccw issue list --json') || '[]');
const history = JSON.parse(Bash('ccw issue history --json 2>/dev/null') || '[]');
const queue = JSON.parse(Bash('ccw issue queue --json 2>/dev/null') || '{}');

// 2. Display summary
console.log(`Active: ${issues.length} | Completed: ${history.length} | Queue: ${queue.pending_count || 0} pending`);

// 3. Ask action via AskUserQuestion
const action = AskUserQuestion({
  questions: [{
    question: 'What would you like to do?',
    header: 'Action',
    options: [
      { label: 'List Issues', description: 'Browse active issues' },
      { label: 'View Issue', description: 'Detail view (includes history)' },
      { label: 'Edit Issue', description: 'Modify fields' },
      { label: 'Bulk Operations', description: 'Batch actions' }
    ]
  }]
});

// 4. Route to handler
Filter Pattern
javascript
const filter = AskUserQuestion({
  questions: [{
    question: 'Filter by status?',
    header: 'Filter',
    multiSelect: true,
    options: [
      { label: 'All', description: 'Show all' },
      { label: 'Registered', description: 'Unplanned' },
      { label: 'Planned', description: 'Has solution' },
      { label: 'Executing', description: 'In progress' }
    ]
  }]
});
Edit Pattern
javascript
// Select field
const field = AskUserQuestion({...});

// Get new value based on field type
// For Priority: show P1-P5 options
// For Status: show status options
// For Title: accept free text via "Other"

// Update file
const issuesPath = '.workflow/issues/issues.jsonl';
// Read → Parse → Update → Write

Data Files

FilePurpose
.workflow/issues/issues.jsonlActive issue records
.workflow/issues/issue-history.jsonlCompleted issues (archived)
.workflow/issues/solutions/<id>.jsonlSolutions per issue
.workflow/issues/queues/index.jsonQueue index (multi-queue)
.workflow/issues/queues/<queue-id>.jsonIndividual queue files

Error Handling

ErrorResolution
No issues foundSuggest /issue:new to create
Issue not foundShow available issues, re-prompt
Write failureCheck file permissions
Queue errorDisplay ccw error message
  • /issue:new - Create structured issue
  • /issue:plan - Generate solution
  • /issue:queue - Form execution queue
  • /issue:execute - Execute tasks

© catlog22, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/issue-manage of catlog22/Claude-Code-Workflow.

Open the folder on GitHubat commit 07491b0

Compare with similar skills

Issue Manage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Issue Manage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Issue Manage this skillcatlog22/Claude-Code-Workflow2.1k—~2.1kAutomated safety check: NotesMIT
Menu Interactionsasmyshlyaev177/react-horizontal-scrolling-menu790—~3.3kAutomated safety check: PassMIT
Remotion Interactivityremotion-dev/remotion62k5 repos~4.8kAutomated safety check: PassCustom licence
Firecrawl Interact Integrationfirecrawl/firecrawl190k1 repos~731Automated safety check: PassISC
Short Menu AutomationComposioHQ/awesome-claude-skills77k3 repos~742Automated safety check: PassNone
Interaction To Next Paintthedaviddias/Front-End-Checklist74k—~441Automated safety check: PassMIT

Similar skills

  • Menu Interactions

    asmyshlyaev177/react-horizontal-scrolling-menu

    Wire mouse, wheel and touch input for react-horizontal-scrolling-menu: onWheel/onScroll are plain (api, event) = void callbacks, while ALL mouse/touch props (onMouseDown, onMouseUp, onMouseMove…

    790 GitHub stars~3.3k tokensUpdated 7 days ago
    Frontend & DesignAuto-check passed
  • Remotion Interactivity

    remotion-dev/remotion

    Official

    Structure Remotion markup for interactivity. An agent skill from remotion-dev/remotion.

    62k GitHub starsUsed in 5 repos~4.8k tokens
    Media & CreativeAuto-check passed
  • Guides adding Firecrawl's /interact endpoint to product code for pages that need clicks, forms, pagination or logged-in flows beyond plain scraping.

    190k GitHub starsUsed in 1 repo~731 tokens
    Data & AnalyticsAuto-check passed
  • Short Menu Automation

    ComposioHQ/awesome-claude-skills

    Automate Short Menu tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~742 tokens
    Productivity & AutomationAuto-check passed
  • Interaction To Next Paint

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Optimize interaction to next paint.

    74k GitHub stars~441 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • Create Issue Interaction UI

    paperclipai/paperclip

    Add a new Paperclip issue-thread interaction kind end-to-end.

    99k GitHub stars~3.4k tokensUpdated today
    Testing & QAAuto-check passed

More from catlog22/Claude-Code-Workflow

All 82 skills in this repo
  • Prompt Generator

    catlog22/Claude-Code-Workflow

    Generate or convert Claude Code prompt files — command orchestrators, skill files, agent role definitions, or style conversion of existing files.

    2.1k GitHub starsUsed in 1 repo~4.7k tokens
    Auto-check: notes
  • Ccw Help

    catlog22/Claude-Code-Workflow

    CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Team Ultra Analyze

    catlog22/Claude-Code-Workflow

    Deep collaborative analysis team skill. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check: notes
  • Brainstorm

    catlog22/Claude-Code-Workflow

    Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.

    2.1k GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Ccw Chain

    catlog22/Claude-Code-Workflow

    Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes
  • Delegation Check

    catlog22/Claude-Code-Workflow

    Check workflow delegation prompts against agent role definitions for content separation violations.

    2.1k GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check: notes

Questions about Issue Manage

What does Issue Manage do?

Interactive issue management with menu-driven CRUD operations. Issue Manage is an agent skill from catlog22/Claude-Code-Workflow. Interactive issue management with menu-driven CRUD operations.

When should I use Issue Manage?

Issue Manage fits situations like: managing issues; viewing issue status; editing issue fields; performing bulk operations.

How do I install Issue Manage in Claude Code?

Run `npx skills add catlog22/Claude-Code-Workflow --skill issue-manage -a claude-code`. Or copy the skill folder (.claude/skills/issue-manage in catlog22/Claude-Code-Workflow) into .claude/skills/issue-manage in your project. Claude Code loads it when a task matches its description.

How do I install Issue Manage in Codex?

Run `npx skills add catlog22/Claude-Code-Workflow --skill issue-manage -a codex`. Or copy the skill folder (.claude/skills/issue-manage in catlog22/Claude-Code-Workflow) into .agents/skills/issue-manage in your project. Codex loads it when a task matches its description.

Can I use Issue Manage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add catlog22/Claude-Code-Workflow --skill issue-manage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-manage, .gemini/skills/issue-manage, .github/skills/issue-manage and .opencode/skills/issue-manage in your project.

What does Issue Manage need to run?

SKILL.md names no scripts, command-line tools or credentials: Issue Manage is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read, Write, AskUserQuestion, Agent, Glob.

Does Issue Manage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Issue Manage safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Issue Manage use?

Issue Manage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Issue Manage use?

About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Issue Manage?

Skills that share tags, products or a category with Issue Manage: Menu Interactions (asmyshlyaev177/react-horizontal-scrolling-menu, 790 stars), Remotion Interactivity (remotion-dev/remotion, 62k stars), Firecrawl Interact Integration (firecrawl/firecrawl, 190k stars) and Short Menu Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Issue Manage?

catlog22 (a GitHub user) maintains it in catlog22/Claude-Code-Workflow, which has 2,130 GitHub stars. The repository holds 82 skills in this directory. The repository was last updated on June 18, 2026.

Source: catlog22/Claude-Code-Workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.