pull_request_template.md
August 10, 2026 · View on GitHub
Problem
Closes #
Prior art — what already exists
-
I reused an existing mechanism. Which one, and how:
-
I extended an existing pattern. Which one, and what I followed:
-
An existing mechanism was close but not sufficient. What I looked at, and specifically why it fell short:
-
This introduces a new module / abstraction. Justify it here:
Tangential updates:
Solution — high level
Deep dive — how it works
Files changed
| File | Why it changed |
|---|---|
path/to/file.py | |
Testing
# commands you ran
-
bash scripts/run_security_tests.shpasses - Added or updated tests covering the new behavior
- If a policy rule changed:
prismor policy validate prismor/runtime/default_policy.yaml - If an integration changed:
bash scripts/verify_registry.sh
Security checklist
- No detection patterns hardcoded in Python — all rules live in YAML
- No real secrets, keys, or credentials in code, tests, fixtures, or docs
- No real secret values printed, logged, or serialized (used
@@SECRET:<name>@@) - No guardrail weakened; if one was, it is called out and justified above
- Docs that describe this behavior (
SKILL.md,docs/,AGENTS.md) are still accurate
Diff size
Lines changed: · Justification if large: