Prompt
Specify a webhook-driven task for OpenClaw
Describe event inputs, validation, deduplication, and intended actions before integration work.
OpenClawDevelopment & Engineering
Dave AI
Codebase Navigation
Use this skill when exploring an unfamiliar codebase, tracing code paths, or answering questions about how the system works. Read before writing, and build a mental model of the architecture before making changes.
instructions.md
--- name: codebase-navigation-eef0a7e9b425 description: Use this skill when exploring an unfamiliar codebase, tracing code paths, or answering questions about how the system works. Read before writing, and build a mental model of the architecture before making changes. category: coding --- # Codebase Navigation Before modifying unfamiliar code, build a mental model. **Exploration strategy:** 1. Start with entry points: `main.py`, `__init__.py`, `index.ts`, `App.tsx`. 2. Follow imports to understand dependency structure. 3. Find the data model first — it shapes everything else. 4. Read tests: they document expected behavior better than comments. 5. Check git log: recent commits explain *why* things are the way they are. **Efficient search:** - Use file pattern search (glob) to find files by name/extension. - Use content search (grep) to find where a function/class is defined vs. called. - Search for the error message text to find the source location directly. **Anti-patterns:** - Modifying code without reading it first. - Assuming file structure from another codebase. - Grepping without a clear hypothesis of what you are looking for.--- name: codebase-navigation-eef0a7e9b425 description: Use this skill when exploring an unfamiliar codebase, tracing code paths, or answering questions about how the system works. Read before writing, and build a mental model of the architecture before making changes. category: coding --- # Codebase Navigation Before modifying unfamiliar code, build a mental model. **Exploration strategy:** 1. Start with entry points: `main.py`, `__init__.py`, `index.ts`, `App.tsx`. 2. Follow imports to understand dependency structure. 3. Find the data model first — it shapes everything else. 4. Read tests: they document expected behavior better than comments. 5. Check git log: recent commits explain *why* things are the way they are. **Efficient search:** - Use file pattern search (glob) to find files by name/extension. - Use content search (grep) to find where a function/class is defined vs. called. - Search for the error message text to find the source location directly. **Anti-patterns:** - Modifying code without reading it first. - Assuming file structure from another codebase. - Grepping without a clear hypothesis of what you are looking for.
Platform guidance
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.