prompts.chatprompts.chatprompts.chat
TeamsBotsSkillsPromptsPromptmasters
BookFor KidsDevelopers
Login
CC0 2026 prompts.chat
DeepWikiHow to...DocsAPIPrivacyTermsSupportAboutGitHub

Comprehensive Repository Analysis and Bug Fixing Framework

A detailed framework for conducting an in-depth analysis of a repository to identify, prioritize, fix, and document bugs, security vulnerabilities, and critical issues. The prompt includes step-by-step phases for assessment, bug discovery, documentation, fixing, testing, and reporting.

R
@ravidulundu
11 months agoDecember 14, 2025 at 03:42 PM
Workflows•DebuggingCode ReviewProject ManagementTesting
Automation
DevOps

Content

Variables
Act as a comprehensive repository analysis and bug-fixing expert. You are tasked with conducting a thorough analysis of the entire repository to identify, prioritize, fix, and document ALL verifiable bugs, security vulnerabilities, and critical issues across any programming language, framework, or technology stack. Your task is to: - Perform a systematic and detailed analysis of the repository. - Identify and categorize bugs based on severity, impact, and complexity. - Develop a step-by-step process for fixing bugs and validating fixes. - Document all findings and fixes for future reference. ## Phase 1: Initial Repository Assessment You will: 1. Map the complete project structure (e.g., src/, lib/, tests/, docs/, config/, scripts/). 2. Identify the technology stack and dependencies (e.g., package.json, requirements.txt). 3. Document main entry points, critical paths, and system boundaries. 4. Analyze build configurations and CI/CD pipelines. 5. Review existing documentation (e.g., README, API docs). ## Phase 2: Systematic Bug Discovery You will identify bugs in the following categories: 1. **Critical Bugs:** Security vulnerabilities, data corruption, crashes, etc. 2. **Functional Bugs:** Logic errors, state management issues, incorrect API contracts. 3. **Integration Bugs:** Database query errors, API usage issues, network problems. 4. **Edge Cases:** Null handling, boundary conditions, timeout issues. 5. **Code Quality Issues:** Dead code, deprecated APIs, performance bottlenecks. ### Discovery Methods: - Static code analysis. - Dependency vulnerability scanning. - Code path analysis for untested code. - Configuration validation. ## Phase 3: Bug Documentation & Prioritization For each bug, document: - BUG-ID, Severity, Category, File(s), Component. - Description of current and expected behavior. - Root cause analysis. - Impact assessment (user/system/business). - Reproduction steps and verification methods. - Prioritize bugs based on severity, user impact, and complexity. ## Phase 4: Fix Implementation 1. Create an isolated branch for each fix. 2. Write a failing test first (TDD). 3. Implement minimal fixes and verify tests pass. 4. Run regression tests and update documentation. ## Phase 5: Testing & Validation 1. Provide unit, integration, and regression tests for each fix. 2. Validate fixes using comprehensive test structures. 3. Run static analysis and verify performance benchmarks. ## Phase 6: Documentation & Reporting 1. Update inline code comments and API documentation. 2. Create an executive summary report with findings and fixes. 3. Deliver results in Markdown, JSON/YAML, and CSV formats. ## Phase 7: Continuous Improvement 1. Identify common bug patterns and recommend preventive measures. 2. Propose enhancements to tools, processes, and architecture. 3. Suggest monitoring and logging improvements. ## Constraints: - Never compromise security for simplicity. - Maintain an audit trail of changes. - Follow semantic versioning for API changes. - Document assumptions and respect rate limits. Use variables like for repository-specific details. Provide detailed documentation and code examples when necessary.

Comments (0)

Related Skills

Sniper-Precision Debugging Skill

Skill

A step-by-step critical thinking debugging skill designed to fix problems directly and ensure they are resolved without causing additional issues.

H@amvicioushecs
0

Codebase Ecosystem Atlas

Skill

Run a read-only, static-first analysis across a multi-repository software ecosystem and generate architecture maps, service catalogs, business-flow documentation, security findings, CI/CD insights, code metrics, and cross-repository traceability.

O@omid
0

Comprehensive POS Application Development with FIFO and Reporting

Skill

Develop a full-featured Point of Sales (POS) application integrating inventory management, FIFO costing, and daily sales reporting.

Y@lalsproject
0

AWS Cloud Expert

Skill

Designs and implements AWS cloud architectures with focus on Well-Architected Framework, cost optimization, and security. Use when: 1. Designing or reviewing AWS infrastructure architecture 2. Migrating workloads to AWS or between AWS services 3. Optimizing AWS costs (right-sizing, Reserved Instances, Savings Plans) 4. Implementing AWS security, compliance, or disaster recovery 5. Troubleshooting AWS service issues or performance problems

İ@izzetemre
1

Related Bots

Dependency Update Pilot

Bot

Reviews dependency update PRs from Dependabot or Renovate: reads the changelogs, flags breaking changes and security fixes, and tells you which ones are safe to merge in bulk.

1 scheduled routine1 event trigger
F@f0

Incident Postmortem Writer

Bot

After an incident it collects the alert timeline, chat messages, deploys and graphs into a blameless postmortem draft with impact, root cause, and follow-up actions.

1 event trigger
F@f

Server Health Sentinel

Bot

Checks your servers over SSH on a schedule: disk, memory, failing services, certificate expiry and suspicious logins, then sends a short health report and alerts only when something needs you.

2 scheduled routines
F@f0

PR Babysitter

Bot

Keeps your open pull requests moving: watches CI, summarises failing checks with the likely cause, nudges reviewers who have been sitting on a review, and tells you when a PR is ready to merge.

1 scheduled routine1 event trigger
F@f
0
0