code-analysis

Analyze code directories for bugs and design flaws, creating GitHub issues.

1|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/Junghyun99/StockAsset --skill code-analysis-junghyun99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-analysis
Source: https://github.com/Junghyun99/StockAsset/tree/main/.claude/skills/code-analysis
Command: npx skills add https://github.com/Junghyun99/StockAsset --skill code-analysis-junghyun99

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying and reporting issues within code, streamlining the bug tracking and code review process.

Core Features & Use Cases

  • Automated Code Review: Analyzes code for bugs, design flaws, and maintainability issues.
  • Issue Creation: Automatically generates GitHub issues for each identified problem.
  • Use Case: Improve code quality by having the AI automatically scan a new feature branch, identify potential bugs or design anti-patterns, and create corresponding GitHub issues for the development team to address.

Quick Start

Use the code-analysis skill to analyze the directory src/core.

Frequently Asked Questions about code-analysis

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

FAQPage Schema
How do I automate code review and create GitHub issues for detected bugs?

Automated code review identifies bugs, design flaws, and maintainability issues by analyzing specified directories, then creates individual GitHub issues for each problem to streamline bug tracking and team resolution.

What is automated code analysis and how does it improve maintainability?

Automated code analysis scans files using Bash commands and retrieval tools to detect design flaws and maintainability issues, streamlining the bug tracking process by automatically generating actionable GitHub issues for development teams.

Do I need the gh CLI installed to automatically generate GitHub issues from code analysis?

Yes, the gh CLI is required for issue creation and management when automating code analysis. The Skill relies on this command-line interface to programmatically generate and manage GitHub issues for identified bugs and design flaws.

Can I analyze a specific directory for bugs instead of the entire codebase?

Yes, code analysis supports targeting specific directories or files. You can direct the analysis to scan a defined path like src/core to identify bugs, design flaws, and maintainability issues within that boundary.

What's the best way to track design flaws found during an automated code review?

The best way to track design flaws is generating individual GitHub issues for each identified problem. This approach streamlines bug tracking by creating actionable tickets directly in your development workflow for the team to address.

Why does automated code analysis create separate GitHub issues for each problem?

Creating individual GitHub issues for each detected bug or maintainability issue ensures granular tracking and targeted resolution. This automated issue creation streamlines the code review process by breaking down complex analysis into actionable development tasks.