What title format does the skill use?

It uses a standardized format: [ ] ( ): , for example: [error] structure(git-workflow): missing plugin.json.

Does this skill work with any GitHub repository?

Yes, it is designed to be project-independent and does not rely on specific local issue templates, making it compatible with any repository.

How does it handle multiple minor warnings?

To avoid clutter, the skill groups warnings and info-level findings from the same category into a single issue containing a checklist, rather than creating separate tickets.

How does it prevent creating the same issue twice?

The skill includes a pre-creation check that searches for existing open issues with the same title pattern using the GitHub CLI.

What is the primary purpose of the Issue Convention skill?

It defines the rules and formats that the project-analyzer uses to transform technical analysis results into well-structured, readable GitHub Issues.

Project Analyzer Issue Convention

Name: Project Analyzer Issue Convention
Author: iamhoonse-dev

byiamhoonse-dev

0•

Collaboration Tools

Standardizes the generation of GitHub Issues from project analysis results with structured templates and grouping logic.

The Issue Convention skill provides a comprehensive framework for converting project analysis data into actionable GitHub Issues. It defines a rigid naming convention following the format `[<severity>] <category>(<scope>): <description>`, handles automatic label assignment, and provides detailed markdown templates for clarity. To prevent notification fatigue and repository clutter, the skill intelligently groups low-priority warnings into checklists while maintaining individual tracking for critical errors. It also includes logic for duplication checking via the GitHub CLI to ensure your issue tracker remains clean and organized.

Key Features

01Intelligent grouping policy for warnings and info-level items

02Standardized issue naming convention with severity, category, and scope

03Comprehensive markdown templates for findings, expected states, and solutions

04Automated label assignment for structure, docs, and settings

050 GitHub stars

06Integrated duplication checks to prevent redundant issue creation

Use Cases

01Maintaining a consistent issue format across different team members and automated tools

02Consolidating multiple documentation warnings into a single maintenance checklist

03Automating the reporting of structural project errors discovered during analysis

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add iamhoonse-dev/hoonse-claude-plugins issue-convention

For use in Claude.ai and ChatGPT

Key Features

01Intelligent grouping policy for warnings and info-level items

02Standardized issue naming convention with severity, category, and scope

03Comprehensive markdown templates for findings, expected states, and solutions

04Automated label assignment for structure, docs, and settings

050 GitHub stars

06Integrated duplication checks to prevent redundant issue creation

Use Cases

01Maintaining a consistent issue format across different team members and automated tools

02Consolidating multiple documentation warnings into a single maintenance checklist

03Automating the reporting of structural project errors discovered during analysis

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add iamhoonse-dev/hoonse-claude-plugins issue-convention

For use in Claude.ai and ChatGPT