findings-to-github-issues

Convert analysis findings into formatted Markdown for GitHub issues and comments.

121|11|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/glaucia86/repocheckai --skill findings-to-github-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: findings-to-github-issues
Source: https://github.com/glaucia86/repocheckai/tree/main/.github/skills/findings-to-github-issues
Command: npx skills add https://github.com/glaucia86/repocheckai --skill findings-to-github-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of converting analysis findings into actionable GitHub issues and pull request comments, saving developers time and ensuring clear communication.

Core Features & Use Cases

  • Automated Formatting: Generates Markdown-ready content for GitHub issues and comments.
  • Categorization: Assigns appropriate labels and prioritizes findings based on predefined rules.
  • Use Case: After running a code analysis tool, use this Skill to automatically create GitHub issues for each critical finding, complete with suggested labels and priority levels, ready for review.

Quick Start

Use the findings-to-github-issues skill to convert the provided list of findings into a GitHub issue.

Frequently Asked Questions about findings-to-github-issues

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

FAQPage Schema
How do I convert code analysis findings into GitHub issues?

To convert code analysis findings into GitHub issues, this Skill transforms raw analysis outputs into formatted Markdown. It structures content, applies labels, and prioritizes findings to generate clear titles and categorized recommendations for efficient tracking.

Can I automate formatting analysis findings for GitHub pull request comments?

Yes, you can automate formatting analysis findings for GitHub pull request comments. This Skill generates Markdown-ready content and structures your analysis output with summarized evidence, creating clear communication ready for review.

How do I categorize and prioritize findings when creating GitHub issues?

To categorize and prioritize findings when creating GitHub issues, this Skill applies predefined rules. It assigns appropriate labels and priority levels automatically, structuring each finding with clear titles and summarized evidence.

What is the best way to structure analysis findings for issue tracking on GitHub?

The best way to structure analysis findings for GitHub issue tracking is to format them as Markdown with categorized recommendations. This Skill handles content structuring and label application to ensure clear and efficient issue creation.

Do I need a specific code analysis tool to generate findings for GitHub issues?

No specific code analysis tool is required. This Skill converts analysis findings from various sources into formatted Markdown for GitHub issues and comments, handling structuring, labels, and prioritization regardless of the originating analysis tool.