Trace a request through a codebase
Follow one request from entry point to storage or external boundary with concrete file references.
Browse reusable instructions for your AI tools. Copy and customize a prompt, or download a skill for a supported agent.

Follow one request from entry point to storage or external boundary with concrete file references.
Reduce a reported defect to a small repeatable case before proposing a fix.
Inspect validation, error contracts, and authorization around one API endpoint.
Derive a focused verification set from changed behavior and affected callers.
Map a dependency upgrade's affected usage and verification needs before changing versions.
Analyze query correctness, parameter handling, and result assumptions using the supplied schema.
Check a supplied component's semantics, keyboard flow, and state announcements.
Find configuration drift without printing secret values or assuming every difference is wrong.
Separate the failing assertion, likely affected behavior, and evidence needed for diagnosis.
Turn a feature request into scope, invariants, acceptance criteria, and concrete completion evidence.
Translate an issue report into a reproducible engineering task without inventing missing evidence.
Give Codex a bounded test failure with a behavior contract and limits on implementation changes.
Draft migration requirements covering mixed versions, existing data, rollback, and validation.
Describe CLI behavior across arguments, streams, exit codes, and machine-readable output.
Frame a review around concrete failure modes, invariants, and affected behavior.
Create a concise repository guide using supplied structure and verified development commands.
Create fixture requirements that isolate behavior and include meaningful boundary cases.
Ask Codex to trace error propagation, cleanup, and caller-visible behavior.
Build one user-visible feature slice while preserving repository conventions and existing work.
Restructure a bounded area while proving important observable behavior stays the same.
Test a real boundary's observable behavior without reproducing its internal implementation.
Find the interleaving that causes stale state, duplicate work, or lost updates.
Review a proposed schema change for data preservation and mixed-version application behavior.
Trace imports, entry points, and data dependencies for a scoped code change.
Try another platform, a broader search, or fewer filters.
Explore all resourcesResource formats: Prompts are ready to copy into a conversation. Skills install into the compatible agent shown on their page.
How it worksInclude the instructions, intended platforms, author, and license. Submissions are reviewed before publication.