- Coding
- Agent
- Intermediate
- Claude Code
- Cursor
- ChatGPT
- Published
Codebase Tour for a Specific Task
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
You get: A research summary
Ready to use: no blanks to fill in.
The prompt
mkdir -p .agents/skills/codebase-tour-for-a-specific-task && curl -sL "https://prompts-gpt.com/prompts/codebase-tour-for-a-specific-task/raw" -o .agents/skills/codebase-tour-for-a-specific-task/SKILL.md---
name: codebase-tour-for-a-specific-task
description: "Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start."
---
# Codebase Tour for a Specific Task
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
## Prompt
```
You are a staff engineer onboarding me to a codebase I do not know. First ask me two short questions: what is the task I need to do, and what do you have access to (the repo, pasted files, or a file tree)? Wait for my answers. Then explore only what matters for that task and ignore the rest. Rules: base every claim on files you actually read and name them; mark anything inferred as an assumption; prefer the real request or data path over generic architecture descriptions; stop at the depth needed for the task. Output format: 1) Task restated in one sentence. 2) Architecture in five sentences or fewer. 3) Key files table with path, role, and why it matters for this task. 4) Data flow as a numbered list from entry point to storage or output. 5) Where to start: the first file to open and the first change to try. 6) Risks and gotchas, such as shared code, config, or missing tests. 7) Open questions to ask a teammate. The tour is good if I could start the task within ten minutes.
```
## Usage Notes
Use when joining an unfamiliar repo with a concrete task. Run it in a tool that can read your repo, or paste the file tree and the files you suspect are relevant.
You are a staff engineer onboarding me to a codebase I do not know. First ask me two short questions: what is the task I need to do, and what do you have access to (the repo, pasted files, or a file tree)? Wait for my answers. Then explore only what matters for that task and ignore the rest. Rules: base every claim on files you actually read and name them; mark anything inferred as an assumption; prefer the real request or data path over generic architecture descriptions; stop at the depth needed for the task. Output format: 1) Task restated in one sentence. 2) Architecture in five sentences or fewer. 3) Key files table with path, role, and why it matters for this task. 4) Data flow as a numbered list from entry point to storage or output. 5) Where to start: the first file to open and the first change to try. 6) Risks and gotchas, such as shared code, config, or missing tests. 7) Open questions to ask a teammate. The tour is good if I could start the task within ten minutes.Example output
Tips and common edits
Use when joining an unfamiliar repo with a concrete task. Run it in a tool that can read your repo, or paste the file tree and the files you suspect are relevant.
Questions about this prompt
More like this
More in CodingCharacterization Tests Before a Refactor
Writes tests that lock in a module's current behavior, including edge cases and quirks, so you can refactor safely.
Failing Test First Bug Fix
Reproduces a bug with a failing test, finds the root cause, applies the smallest fix and shows the test passing.
Architecture Decision Record for a Technology Choice
Compares realistic options against your constraints and produces a decision record. The record has a weighted comparison, risks, a reversal plan, and a recommendation the team can approve or challenge.
Pull Request Review with Merge Recommendation
Reviews a diff against your standards and returns a merge, merge-with-changes, or do-not-merge recommendation. Findings are ranked by severity, with evidence, suggested fixes, and open questions.
Root Cause Analysis from Stack Trace and Logs
Turns an error report, stack trace, and logs into ranked root-cause hypotheses. Includes the cheapest checks to confirm each one, a fix proposal, and a regression test plan.
Unit Test Plan and Test Code for an Existing Function
Builds a behavior-based test matrix for a function or module and then generates test code in your framework. Covers edge cases, failures, and mocking boundaries, with coverage gaps stated honestly.
Explain This Error with Ranked Causes
Explains an error and stack trace in plain words, ranks the three most likely causes and gives a confirming check for each.
Regex with Match and Non-Match Test Strings
Writes a regex for your pattern, explains each part and provides 8 strings that should match and 8 that should not.
SQL Query from Schema and Question
Writes a SQL query that answers your question from your schema, explains each clause and suggests indexes worth adding.
Cursor .mdc Rules to Portable AGENTS.md Converter
Converts your pasted Cursor .mdc rules into a single AGENTS.md that Codex, Copilot and Gemini CLI can read, plus a table of what does not carry over.
Explain a Codebase Folder to a New Developer on Their First Day
Produces an onboarding guide for one folder of a codebase: what it does, how data moves through it, the files to read first and the traps a new developer should avoid.
90-Day Lifecycle Marketing Diagnostic and Experiment Roadmap for Onboarding and Retention
Diagnoses drop-off across the customer lifecycle from your funnel data and produces a prioritized 90-day plan of messages, triggers, and experiments with metrics so teams can decide where to invest first.