A detailed framework for conducting an in-depth analysis

Comprehensive repository analysis and bug fixing framework

by Ravi DULUNDU · CC0-1.0 license · updated Sep 9

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…

Overview

The prompt

67 lines · 3,195 characters · paste it into ChatGPT, Claude or Gemini

1	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.
2
3	Your task is to:
4	- Perform a systematic and detailed analysis of the repository.
5	- Identify and categorize bugs based on severity, impact, and complexity.
6	- Develop a step-by-step process for fixing bugs and validating fixes.
7	- Document all findings and fixes for future reference.
8
9	## Phase 1: Initial Repository Assessment
10	You will:
11	1. Map the complete project structure (e.g., src/, lib/, tests/, docs/, config/, scripts/).
12	2. Identify the technology stack and dependencies (e.g., package.json, requirements.txt).
13	3. Document main entry points, critical paths, and system boundaries.
14	4. Analyze build configurations and CI/CD pipelines.
15	5. Review existing documentation (e.g., README, API docs).
16
17	## Phase 2: Systematic Bug Discovery
18	You will identify bugs in the following categories:
19	1. Critical Bugs: Security vulnerabilities, data corruption, crashes, etc.
20	2. Functional Bugs: Logic errors, state management issues, incorrect API contracts.
21	3. Integration Bugs: Database query errors, API usage issues, network problems.
22	4. Edge Cases: Null handling, boundary conditions, timeout issues.
23	5. Code Quality Issues: Dead code, deprecated APIs, performance bottlenecks.
24
25	### Discovery Methods:
26	- Static code analysis.
27	- Dependency vulnerability scanning.
28	- Code path analysis for untested code.
29	- Configuration validation.
30
31	## Phase 3: Bug Documentation & Prioritization
32	For each bug, document:
33	- BUG-ID, Severity, Category, File(s), Component.
34	- Description of current and expected behavior.
35	- Root cause analysis.
36	- Impact assessment (user/system/business).
37	- Reproduction steps and verification methods.
38	- Prioritize bugs based on severity, user impact, and complexity.
39
40	## Phase 4: Fix Implementation
41	1. Create an isolated branch for each fix.
42	2. Write a failing test first (TDD).
43	3. Implement minimal fixes and verify tests pass.
44	4. Run regression tests and update documentation.
45
46	## Phase 5: Testing & Validation
47	1. Provide unit, integration, and regression tests for each fix.
48	2. Validate fixes using comprehensive test structures.
49	3. Run static analysis and verify performance benchmarks.
50
51	## Phase 6: Documentation & Reporting
52	1. Update inline code comments and API documentation.
53	2. Create an executive summary report with findings and fixes.
54	3. Deliver results in Markdown, JSON/YAML, and CSV formats.
55
56	## Phase 7: Continuous Improvement
57	1. Identify common bug patterns and recommend preventive measures.
58	2. Propose enhancements to tools, processes, and architecture.
59	3. Suggest monitoring and logging improvements.
60
61	## Constraints:
62	- Never compromise security for simplicity.
63	- Maintain an audit trail of changes.
64	- Follow semantic versioning for API changes.
65	- Document assumptions and respect rate limits.
66
67	Use variables like ${repositoryName} for repository-specific details. Provide detailed documentation and code examples when necessary.