Files
superpowers/.github/PULL_REQUEST_TEMPLATE.md
Jesse Vincent 6fd4507659 Require contributors to disclose authoring environment and target dev
Add a mandatory self-identification disclosure (model, harness, harness
version, all installed plugins) to the PR template and all three issue
templates, and document the requirement in the contributor guidelines.
We weigh contributions differently depending on what produced them:
content reasoned from documentation is held to a different bar than work
grounded in a real session.

Also state explicitly, in both CLAUDE.md and the PR template, that all
PRs must target the dev branch rather than main.
2026-05-29 13:05:25 -07:00

5.7 KiB

This PR MUST target the dev branch, not main. main is the released branch; active work lands on dev first. PRs opened against main will be asked to retarget dev before review.

Who is submitting this PR? (required)

Field Value
Your model + version
Harness + version
All plugins installed
Human partner who reviewed this diff

What problem are you trying to solve?

What does this PR change?

Is this change appropriate for the core library?

What alternatives did you consider?

Does this PR contain multiple unrelated changes?

Existing PRs

  • I have reviewed all open AND closed PRs for duplicates or prior art
  • Related PRs:

Environment tested

Harness (e.g. Claude Code, Cursor) Harness version Model Model version/ID

New harness support (required if this PR adds a new harness)

Clean-session transcript for "Let's make a react todo list"
paste the complete transcript here

Evaluation

  • What was the initial prompt you (or your human partner) used to start the session that led to this change?
  • How many eval sessions did you run AFTER making the change?
  • How did outcomes change compared to before the change?

Rigor

  • If this is a skills change: I used superpowers:writing-skills and completed adversarial pressure testing (paste results below)
  • This change was tested adversarially, not just on the happy path
  • I did not modify carefully-tuned content (Red Flags table, rationalizations, "human partner" language) without extensive evals showing the change is an improvement

Human review

  • A human has reviewed the COMPLETE proposed diff before submission