create-issue-description

Name: create-issue-description
Availability: InStock
Author: unfoldingWord

Create or update translation issue description files with YAML frontmatter and required sections.

1|Updated Mar 25, 2026

Search Tags:#templates #documentation #create #data-management #issue-identification #translation-issues #ta-articles

Ready to run

npx skills add https://github.com/unfoldingWord/bp-assistant-skills --skill create-issue-description

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates or updates a translation issue description file for the issue-identification skill set, enabling consistent documentation of new issue types or figures of speech.

Core Features & Use Cases

Document new translation issues by producing a structured description that aligns with the translation issues data and TA sources.
Update existing issue descriptions when guidelines or nomenclature changes, ensuring consistency across data sources and templates.
Use when asked to create or document how to identify a specific translation issue type.

Quick Start

Ask Claude to create or update an issue description for a target translation issue label.

Frequently Asked Questions about create-issue-description

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

FAQPage Schema

How do I create a structured translation issue description for documenting new figures of speech?▼

To create a translation issue description, use this skill to generate a structured file that aligns with translation issues data and TA sources. It enforces naming conventions, ensures YAML frontmatter presence, and structures guidance with required sections for downstream loading.

What is the process for updating translation issue descriptions when nomenclature changes?▼

Updating translation issue descriptions involves modifying the existing file to reflect guideline or nomenclature changes. The skill ensures consistency across related data sources such as data/translation-issues.csv, TA articles, and TN notes during the update.

How does YAML frontmatter enforcement work for translation issue identification files?▼

YAML frontmatter enforcement ensures translation issue description files contain required metadata headers. The skill validates frontmatter presence and enforces naming conventions so downstream loading processes can correctly parse and identify translation issue types.

Do I need existing translation-issues.csv data to document a new translation issue type?▼

Documenting a new translation issue type works best when updating related data sources like data/translation-issues.csv alongside TA articles and TN notes. The skill structures the description to align with these existing data and template sources for consistency.

What's the best way to structure guidance sections for a translation issue description file?▼

The best way to structure guidance sections is to follow the required formatting enforced by the skill. It produces a structured description file with standardized sections that align with translation issues data, ensuring proper downstream loading and issue identification.