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.
25 prompts
Prompts for Cursor, the AI code editor. They are written for its agent and chat, and name the files, the change and the checks, so the edit lands where you expect it.
3 results
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
A SKILL.md that writes release notes from the commits between two tags, split into a plain-language section for users and a technical changelog for developers.
A SKILL.md that forces your coding agent to reproduce a bug with a failing test before changing code, apply the smallest fix, and prove it with the test suite.
Open the chat panel, choose Agent when the task changes several files, and paste the prompt. Mention files with @ so Cursor reads them before it plans the edit.
Only the parts that apply to every task. Project rules live in the repository's .cursor/rules folder; one-off task prompts belong in the chat.
No. Cursor lets you choose the model, and the prompts are plain instructions that any capable model can follow. A stronger model helps most on changes across many files.