make-github-issues

Analyze codebases and create labeled GitHub issues with duplicate checks.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill make-github-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-github-issues
Source: https://github.com/stevengonsalvez/nanoclaw-standalone/tree/main/container/skills/make-github-issues
Command: npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill make-github-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review codebases to identify defects, design issues, and technical debt and turn findings into actionable GitHub issues to accelerate remediation and tracking.

Core Features & Use Cases

  • Automated discovery: Scans the codebase for bugs, design flaws, and quality issues across specified scope or the whole project.
  • Issue generation: Creates GitHub issues with structured titles, descriptions, and precise code locations; supports labels and assignees.
  • Duplicate detection & reporting: Checks for existing issues to avoid duplicates and produces a concise code-review-findings summary.
  • Use Case: A team runs a weekly code-quality review and converts each finding into tracked GitHub issues for accountability.

Quick Start

Run the make-github-issues skill against the target repository or path to initiate analysis and issue creation.

Frequently Asked Questions about make-github-issues

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

FAQPage Schema
How do I automate GitHub issue creation from code review findings?▼

The skill scans your codebase for bugs, design flaws, code quality problems, security risks, and technical debt, then generates a structured GitHub issue for each finding with titles, descriptions, labels, and precise code locations.

What types of code issues can be tracked automatically in GitHub?▼

Automated code review tracking can identify bugs, design issues, code quality problems, security risks, and technical debt across targeted scopes or the entire project for comprehensive remediation.

How do I avoid creating duplicate GitHub issues during automated code analysis?▼

To avoid duplicate GitHub issues during automated code analysis, the skill checks for existing issues before creating new ones, ensuring only unique findings are tracked while generating a summary report.

Can I scan specific directories for security risks and tech debt instead of the whole project?▼

Yes, you can target specific directories for security risks and technical debt by applying the analysis to specified scopes like targeted files or directories, rather than performing a comprehensive review across the entire project.

Does automated code review generate a summary of the GitHub issues created?▼

Automated code review generates a code-review-findings.md summary file containing concise details of the analysis and direct links to all created GitHub issues for streamlined tracking.