Prompt Template Library

Act as a senior software engineer with strong code review skills.

Audience: {{audience, e.g. the developer who wrote the code}}

Review the following {{language}} code for correctness, readability, and maintainability. Point out bugs, edge cases, and security issues. Suggest concrete improvements with code examples.

Context: {{what the code does / where it's used}}

Code:
{{paste code here}}

Length: {{desired length, e.g. under 300 words}}
Format: {{how the response should be structured, e.g. numbered steps, a table, bullet points with headers}}

Act as a senior software engineer skilled at debugging {{language/framework}} issues.

Audience: {{audience, e.g. yourself, or a teammate helping you troubleshoot}}

I'm getting the following error in {{language/framework}}:

{{paste error message and stack trace}}

Relevant code:
{{paste relevant code}}

What I've already tried: {{steps tried}}

Explain the likely root cause and give me a fix.

Length: {{desired length, e.g. under 300 words}}
Format: {{how the response should be structured, e.g. numbered steps, a table, bullet points with headers}}

Act as a senior software engineer focused on test coverage and code quality.

Audience: {{audience, e.g. your team's codebase / CI pipeline}}

Write unit tests for the following function using {{testing framework, e.g. Jest}}. Cover the happy path, edge cases, and error conditions. Use clear, descriptive test names.

Function:
{{paste function}}

Length: {{desired length, e.g. under 300 words}}
Format: {{how the response should be structured, e.g. numbered steps, a table, bullet points with headers}}

Act as a senior software engineer experienced in clean code practices.

Audience: {{audience, e.g. teammates who will maintain this code}}

Refactor this {{language}} code to improve readability and reduce complexity without changing its behavior. Keep the public API the same. Explain each change briefly.

Code:
{{paste code}}

Length: {{desired length, e.g. under 300 words}}
Format: {{how the response should be structured, e.g. numbered steps, a table, bullet points with headers}}

Act as a senior software engineer writing a pull request.

Audience: {{audience, e.g. your code reviewers and teammates}}

Write a clear pull request description for the following change. Include: a one-line summary, what changed and why, how to test it, and any risks or follow-ups.

Diff / summary of changes:
{{paste diff or bullet list of changes}}

Ticket/issue: {{link or ID}}

Length: {{desired length, e.g. under 300 words}}
Format: {{how the response should be structured, e.g. numbered steps, a table, bullet points with headers}}

Act as a senior software engineer writing developer-facing documentation.

Audience: {{audience, e.g. external developers integrating with this API}}

Write API documentation for the following endpoint/function. Include: purpose, parameters (with types and whether required), return value/response shape, and one example request and response.

Endpoint/function:
{{paste signature, route, or code}}

Length: {{desired length, e.g. under 300 words}}
Format: {{how the response should be structured, e.g. numbered steps, a table, bullet points with headers}}