bug-report

Analyze code repositories to identify and document bugs by severity.

12|Updated Mar 3, 2026

Search Tags:#code review #code analysis #debugging #security audit #issue tracking #bug report

Ready to run

npx skills add https://github.com/KilimcininKorOglu/cli-tweaks --skill bug-report-kilimcininkoroglu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/KilimcininKorOglu/cli-tweaks/tree/main/claude/skills/bug-report
Command: npx skills add https://github.com/KilimcininKorOglu/cli-tweaks --skill bug-report-kilimcininkoroglu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of identifying, analyzing, and documenting bugs within a codebase, providing a structured report for efficient issue resolution.

Core Features & Use Cases

Comprehensive Bug Discovery: Scans repositories for various bug categories across different severity levels.
Systematic Documentation: Generates detailed bug reports with severity, status, file location, and root cause analysis.
Use Case: When a critical security vulnerability is suspected, this Skill can be invoked to perform a thorough audit, identify the vulnerability, and generate a report detailing its severity and location.

Quick Start

Run a full analysis of the repository to find and report all bugs.

Frequently Asked Questions about bug-report

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

FAQPage Schema

How do I automate code analysis to find bugs across an entire repository?▼

To perform a security audit, the codebase is scanned to identify vulnerabilities, assess project structure, and generate detailed bug reports documenting severity, status, and exact file locations for suspected security flaws.

How does systematic bug reporting work for issue tracking?▼

Systematic bug reporting works by analyzing the codebase to discover issues, then generating structured documentation that categorizes each bug by severity, status, and root cause to streamline issue tracking and resolution.

Can I use this for code reviews to identify security vulnerabilities?▼

Yes, you can use this for code reviews to identify security vulnerabilities. It performs thorough audits across the codebase, evaluates existing issues, and documents security flaws with detailed severity assessments and file locations.

What is the best way to document code bugs found during a security audit?▼

The best way to document code bugs found during a security audit is to generate a structured report detailing each bug's severity, status, file location, and root cause analysis, ensuring efficient issue resolution.

Does bug hunting require assessing the project structure and technology stack?▼

Yes, effective bug hunting requires assessing the project structure and technology stack. This contextual evaluation allows the analysis to systematically scope security audits and accurately identify bugs across the codebase.