Menu
PR creation template for consistent, well-structured pull requests. Use when opening a PR.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Safety rules for modifying Dockerfiles and Containerfiles. Use when editing container build files.
MR/PR context gathering and diagnostic reporting guidelines. Activates when working on events that reference MRs/PRs or when reporting investigation findings.
Team coordination for implement and test modes. Developer and QE use team_send_results for final reports, team_huddle for mid-task questions to FRIDAY.
GitOps workflow rules for modifying infrastructure via git. Use when cloning repos, modifying Helm values, committing, pushing, or verifying deployments.
MR/PR lifecycle operations -- pipeline check, retest, merge, conflict reporting. Extends darwin-gitlab-ops.
Report findings and status updates to the Darwin FRIDAY. Use team_send_results for final reports (task modes). In message mode, use team_send_message instead.
| name | darwin-pr-template |
| description | PR creation template for consistent, well-structured pull requests. Use when opening a PR. |
| roles | ["developer"] |
| modes | ["implement"] |
When creating a pull request, use this structure:
feat: <short description> (evt-{EVENT_ID})
Examples:
feat: add admin authentication with session cookies (evt-78fe9a5f)feat: add product reviews and detail modal (evt-ed3ed4fa)## Summary
<1-2 sentences: what this PR does and why>
## Changes
- `file.py` -- <what changed>
- `file.html` -- <what changed>
## Testing
- <how this was tested locally>
- <which tests were added>
## Event
evt-{EVENT_ID}
feat: for features or fix: for bug fixes