issue-create

Create numbered issue files in doc/issues/ with frontmatter from CLAUDE.md rules.

1|Updated Jan 29, 2015

Search Tags:#automation #versioning #documentation #ticket #issue #project-management #file-naming

Ready to run

npx skills add https://github.com/hayamiz/catscope --skill issue-create-hayamiz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-create
Source: https://github.com/hayamiz/catscope/tree/main/.claude/skills/issue-create
Command: npx skills add https://github.com/hayamiz/catscope --skill issue-create-hayamiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Issue creation often lacks consistency and proper metadata. This Skill ensures new issues follow project conventions and frontmatter templates.

Core Features & Use Cases

Deterministic numbering: scans doc/issues/ and doc/issues/resolved/ for NNNN-*.md and computes the next number.
Frontmatter templating: uses CLAUDE.md rules to structure the issue file with required fields.
Lightweight workflow: creates ready-to-edit issue files aligned with project governance.

Quick Start

Create a new issue in doc/issues/ using the next available number and the defined template.

Frequently Asked Questions about issue-create

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

FAQPage Schema

How do I automatically create standardized issue files for project management?▼

To automatically create standardized issue files, this Skill generates new tickets in doc/issues/ using a deterministic numbering scheme and frontmatter template defined by your project's CLAUDE.md conventions. It scans existing and resolved issues to compute the next available NNNN-<subject>.md file name.

What's the best way to ensure consistent file naming for bug and feature tickets?▼

Ensuring consistent file naming for tickets is handled by a deterministic numbering scheme that scans doc/issues/ and doc/issues/resolved/ to compute the next available number. This guarantees sequential NNNN-<subject>.md file names without manual tracking or naming conflicts.

How does deterministic issue numbering work when logging project tasks?▼

Deterministic issue numbering works by scanning the doc/issues/ and doc/issues/resolved/ directories for existing NNNN-*.md files. It then calculates the next available integer in the sequence, applying it to the new issue file name to prevent duplicate ticket numbers.

Do I need a specific folder structure to generate issue files with frontmatter?▼

Yes, generating issue files requires a doc/issues/ directory structure for active tickets and optionally doc/issues/resolved/ for closed ones. The Skill also relies on CLAUDE.md rules to structure the required frontmatter fields and body content for project governance compliance.

Can I use this to log bugs, features, and tasks with a standardized template?▼

Yes, you can use this to log bugs, features, and tasks. It applies a standardized frontmatter template governed by your CLAUDE.md rules, creating ready-to-edit issue files that align with project conventions and ensure proper metadata capture for tracking.

Why are my manually created issue files missing required frontmatter metadata?▼

Manually created issue files often lack required frontmatter metadata because they bypass project governance rules. This Skill enforces CLAUDE.md frontmatter templating during issue creation, ensuring every new ticket includes necessary structural fields for consistent project management documentation.