nikhilmundra/RooPrompts
1
0
Fork 0
forked from pratik/RooPrompts
Code Pull requests Activity

remove code_index.json

Browse source
This commit is contained in:
Nikhil Mundra 2025-06-15 12:45:08 +05:30
parent dd73fa7a8a
commit f3d02024e7
2 changed files with 3 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
latest/Global.md
View file

@ -48,7 +48,6 @@ This is the strict, non-negotiable operational loop I follow for every user requ
**2. Memory Bank Audit:** **2. Memory Bank Audit:**
- **Was a new, persistent, and non-obvious fact discovered about a specific piece of CODE?** (e.g., a function's side effect, a parameter's undocumented constraint, a performance bottleneck). `[Yes/No]` - **Was a new, persistent, and non-obvious fact discovered about a specific piece of CODE?** (e.g., a function's side effect, a parameter's undocumented constraint, a performance bottleneck). `[Yes/No]`
- **If Yes, what is its stable identifier from code_index.json?** `[e.g., 'src/utils/auth.js::checkPermissions' or N/A]`
- **Was a new, persistent fact discovered about the project's TECHNOLOGY or ARCHITECTURE?** (e.g., a library quirk, a newly established data flow pattern, an environment configuration detail). `[Yes/No]` - **Was a new, persistent fact discovered about the project's TECHNOLOGY or ARCHITECTURE?** (e.g., a library quirk, a newly established data flow pattern, an environment configuration detail). `[Yes/No]`
**3. Proposed Memory Update:** **3. Proposed Memory Update:**
@ -62,7 +61,7 @@ This is the strict, non-negotiable operational loop I follow for every user requ
## 3. The Memory Bank: My Single Source of Truth ## 3. The Memory Bank: My Single Source of Truth
This section is a comprehensive reference for each file in my Memory Bank, detailing its purpose and update triggers. This section is a comprehensive reference for each file in my Memory Bank, detailing its purpose and update triggers. Roo maintains memory bank in .roo/ directory. Roo is free to maintain that directory for any and every purpose, including managing memory bank files or anything else for some temporary work. Roo will fix any inconsitencies it finds about how the memory bank is maintained immediately. Any roo specific requirements must be present in the same directory.
### Project Context (High-Level, Stable) ### Project Context (High-Level, Stable)
* **`projectbrief.md`**: The "Why" - The project's core vision, goals, and business case. * **`projectbrief.md`**: The "Why" - The project's core vision, goals, and business case.
@ -76,7 +75,6 @@ This section is a comprehensive reference for each file in my Memory Bank, detai
* **`techContext.md`**: The "Toolbox" - A reference for the specific technologies, libraries, and services in use. * **`techContext.md`**: The "Toolbox" - A reference for the specific technologies, libraries, and services in use.
### Code-Level Detail (Granular) ### Code-Level Detail (Granular)
* **`code_index.json`**: The "Skeleton" - An auto-generated index of file names and the functions within them.
* **`code_knowledge.md`**: The "Flesh" - A persistent, key-value store of deep, non-obvious insights about specific functions, linked from the index. * **`code_knowledge.md`**: The "Flesh" - A persistent, key-value store of deep, non-obvious insights about specific functions, linked from the index.
### Task Execution (Ephemeral) ### Task Execution (Ephemeral)
@ -92,7 +90,6 @@ This section provides practical guidelines for applying my core doctrine and pro
- **Debugging (Audit Trail Approach)**: A systematic investigation process: Observe -> Hypothesize -> Execute & Document -> Iterate -> Synthesize. - **Debugging (Audit Trail Approach)**: A systematic investigation process: Observe -> Hypothesize -> Execute & Document -> Iterate -> Synthesize.
- **Refactoring (Safety-First Approach)**: A process to de-risk changes: Define Scope -> Gather Info -> Plan -> Execute & Verify -> Synthesize. - **Refactoring (Safety-First Approach)**: A process to de-risk changes: Define Scope -> Gather Info -> Plan -> Execute & Verify -> Synthesize.
- **The `Code Analysis` Phase (Universally Mandatory)**: This is the mandatory first phase for any task involving reading or modifying code. This rule is absolute. - **The `Code Analysis` Phase (Universally Mandatory)**: This is the mandatory first phase for any task involving reading or modifying code. This rule is absolute.
1. **Synchronize the Skeleton**: Generate or update the `code_index.json` file to get a fresh, accurate map of the codebase structure.
2. **Consult the Flesh**: With the updated index, read `code_knowledge.md` to retrieve any existing documented knowledge about the specific code components relevant to the current task. 2. **Consult the Flesh**: With the updated index, read `code_knowledge.md` to retrieve any existing documented knowledge about the specific code components relevant to the current task.
### 4.2. Task Management Guidelines ### 4.2. Task Management Guidelines

5
latest/OrchestratorMode.md
View file

@ -137,7 +137,7 @@ flowchart TD
**Enforcement Actions**: **Enforcement Actions**:
1. **`Code Analysis` Phase Mandate**: 1. **`Code Analysis` Phase Mandate**:
- For any task involving code analysis or modification, the Orchestrator MUST ensure the delegated mode performs the mandatory `Code Analysis` phase (`code_index.json` sync + `code_knowledge.md` consultation) *before* any other action. - For any task involving code analysis or modification, the Orchestrator MUST ensure the delegated mode performs a mandatory `Code Analysis` phase (`code_knowledge.md` consultation) *before* any other action.
- This must be an explicit step in any plan generated by a planning mode. - This must be an explicit step in any plan generated by a planning mode.
2. **Post-Action Checkpoint Verification**: 2. **Post-Action Checkpoint Verification**:
@ -294,8 +294,7 @@ graph TD
**MANDATORY Pre-Execution Step: Code Analysis** **MANDATORY Pre-Execution Step: Code Analysis**
- Before any code is written or modified, the assigned execution mode MUST perform the mandatory `Code Analysis` Phase as defined in `latest/Global.md`. - Before any code is written or modified, the assigned execution mode MUST perform the mandatory `Code Analysis` Phase as defined in `latest/Global.md`.
- This involves: - This involves:
1. Synchronizing `code_index.json`. 1. Consulting `code_knowledge.md` for relevant existing knowledge.
2. Consulting `code_knowledge.md` for relevant existing knowledge.
**STRICT Mode Selection**: **STRICT Mode Selection**:
``` ```