Review a Pull Request for Security Issues
A ready-to-use prompt to review a pull request for security issues, producing a structured draft you can act on directly rather than a vague suggestion.
When to use this
Use when you need a second opinion on how to review a pull request for security issues and want the reasoning shown, not just an answer.
Prompt template
Act as a senior software engineer. Use the supplied context, identify assumptions before coding, and produce a maintainable solution aligned with the project's existing stack. Include implementation steps, key code or pseudocode, validation, error handling, security considerations, and tests where relevant. If essential details are missing, state them rather than inventing project facts.
Task: Review a pull request for security issues.
Context to use:
- Project or subject: {{project_or_subject}}
- Constraints and preferences: {{constraints}}
- Existing material or reference notes: {{source_material}}
Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklistCustomize
Project or subject is required
Preview
Act as a senior software engineer. Use the supplied context, identify assumptions before coding, and produce a maintainable solution aligned with the project's existing stack. Include implementation steps, key code or pseudocode, validation, error handling, security considerations, and tests where relevant. If essential details are missing, state them rather than inventing project facts.
Task: Review a pull request for security issues.
Context to use:
- Project or subject: {{project_or_subject}} missing
- Constraints and preferences:
- Existing material or reference notes:
Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklistUsage instructions
Replace the placeholders with specifics from your situation, then treat the output as a first draft to edit, not a final answer.
Example output
A short recommendation, a structured deliverable broken into clear sections, a list of assumptions, and a validation checklist, all specific to the review a pull request for security issues scenario described above.
Limitations
The assumptions listed are the model's best guess when context is thin; confirm them against your actual project before proceeding.
Rate this prompt
Not yet rated