skills.rest
ywj3493
ywj3493COMMUNITY
Explore all skills by this author →
GitHub

new-issue

Generate numbered bilingual issue documents in Markdown for English and Korean.

2|Updated Feb 17, 2026
Search Tags:#workflow#documentation#markdown#task management#issue tracking#bilingual
One-click install
npx skills add https://github.com/ywj3493/claude-skills --skill new-issue-ywj3493
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-issue
Source: https://github.com/ywj3493/claude-skills/tree/main/skills/new-issue
Command: npx skills add https://github.com/ywj3493/claude-skills --skill new-issue-ywj3493

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating new issue documents, ensuring consistency and bilingual support for tracking work items like features, bug fixes, and tasks.

Core Features & Use Cases

  • Automated Issue Numbering: Automatically determines the next available issue number.
  • Bilingual Document Generation: Creates both English and Korean versions of the issue document.
  • Use Case: When starting a new feature development, you can use this skill to quickly generate issue001.md in English and 이슈 001.md in Korean, complete with sections for background, acceptance criteria, and tasks.

Quick Start

Use the new-issue skill to create a new issue for tracking a bug fix.

Frequently Asked Questions about new-issue

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

FAQPage Schema
How do I create bilingual task tracking documents in Markdown?▼

Bilingual issue documents in Markdown are generated by creating corresponding files in separate language directories like docs/en/issue/ and docs/ko/issue/ for English and Korean. This ensures consistent tracking of work items across both languages.

How does automated issue numbering work for Markdown files?▼

Automated issue numbering works by scanning existing Markdown files in the issue directory to determine the next sequential number. It assigns this next available number to the new document, preventing duplicate tracking identifiers.

Can I generate issue documents for both English and Korean workflows?▼

Yes, you can generate issue documents for both English and Korean workflows. The process creates corresponding Markdown files in the docs/en/issue/ and docs/ko/issue/ directories to support bilingual tracking requirements.

What is the best way to track bug fixes and features using Markdown issues?▼

The best way to track bug fixes and features using Markdown issues is to generate standardized documents with sections for background, acceptance criteria, and tasks. This ensures consistency and bilingual support for all tracked work items.

Do I need a specific directory structure to generate bilingual issues?▼

Yes, you need the docs/en/issue/ and docs/ko/issue/ directory structure to generate bilingual issues. The process relies on these specific paths to correctly place the English and Korean Markdown files for issue tracking.

Related Skills

Explore More Software Engineering Skills→
bacchus-labsbacchus-labs
4

refreshing-metrics

Refresh governance metrics in markdown documents from MCP issue data.

Official
Advanced
OmniNode-aiOmniNode-ai
3

insights-to-plan

Parse Claude Code insights HTML reports into prioritized design plans with acceptance criteria.

Official
Advanced
anhhung04anhhung04
1

github-triage

Automate task creation and status updates from GitHub issues via the API.

Community
Basic
gotgenesgotgenes
143

markdown-conventions

Enforce project-specific Markdown rules and YAML frontmatter schema during writing.

Community
Intermediate