issue-management_skill

This skill provides comprehensive GitHub issue CRUD with templates, metadata, and context awareness to streamline creation, updates, and linking.
  • TypeScript

4

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill constellos/claude-code --skill issue-management

  • SKILL.md9.1 KB

Overview

This skill provides comprehensive GitHub issue lifecycle management with templates, metadata controls, and context-aware automation. Use it to create, update, label, assign, link, and close issues with consistent structure and optional templates. It complements automatic hooks by offering direct, manual control when you need specific templates or bulk operations.

How this skill works

The skill exposes utilities for rendering structured templates (bug, feature, epic, task) and for creating or editing issues via GitHub CLI patterns. It detects context from branch names, state files, detected work type, and session info to suggest labels and linkages automatically. It also supports searching, bulk creation, adding branch references, and maintaining mapping state files under .claude/logs.

When to use it

  • Create issues with predefined templates or custom rendered bodies
  • Update labels, assignees, milestones, or the issue body after creation
  • Link issues as parent-child or related and add branch references
  • Search and filter issues before creating to avoid duplicates
  • Create or update multiple issues at once or sync plan files to issues

Best practices

  • Use templates for reproducible, reviewable issue content
  • Detect and apply work-type labels automatically from titles/descriptions
  • Search existing issues first to prevent duplicates
  • Link parent/child and related issues to preserve traceability
  • Keep .claude/logs state files updated when creating or syncing issues

Example use cases

  • Create a bug report using getBugTemplate() and renderTemplate() with repro steps and environment details
  • Turn a plan file into an epic issue and save the mapping in plan-issues.json
  • Detect work type from a title and add corresponding labels like bug or enhancement
  • Bulk-create related tasks for an epic using a small script and consistent labels
  • Update an issue with branch info and post progress comments when switching branches

FAQ

Work-type detection analyzes title and body keywords to suggest standardized labels like bug, feature, docs, refactor, or chore, reducing manual label decisions.

Can I link issues automatically when creating an epic?

Yes—create the epic with a subtasks checklist and reference child issue numbers in the body, then save mappings to .claude/logs to keep relationships discoverable.

What state files should I keep in sync?

Keep .claude/logs/plan-issues.json and .claude/logs/branch-issues.json updated when you manually create or link issues so hooks and tools can reference accurate mappings.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
issue-management skill by constellos/claude-code | VeilStrat