[hivecommons-hive]

Summary

Adds .github/pull_request_template.md so contributors see pluk's contribution rules when they open a PR. Until now those rules appeared only in CONTRIBUTING.md. The layout (Summary / Validation / Checklist) matches the templates in rationguard, promptargs, dibs, hotshot and homebrew-hive.

Closes #378

Claim evidence

Each checklist line restates an existing rule and adds no new requirement:

• npm test builds first and enforces lines 99 / branches 96 / functions 98: CONTRIBUTING.md "Local development"; package.json scripts.test.
• changelog.d/<category>-<slug>.md fragment, six categories, bullet body: CONTRIBUTING.md "Making changes"; enforced by test/changelog-fragments.test.js.
• README examples updated when CLI behavior or flags change: CONTRIBUTING.md "Making changes".
• patterns/<cli>.patterns must match the inline constant in src/patterns.ts: CONTRIBUTING.md "Fixing an existing pattern set" step 2; test/patterns.test.js.
• The "Adding a new CLI" file table: CONTRIBUTING.md; test/cli-support-matrix.test.js.
• No committed dist/: CONTRIBUTING.md "Making changes".
• DCO sign-off: CONTRIBUTING.md "Developer Certificate of Origin".
• Security reports go through SECURITY.md: the file exists at the repo root.

Validation

This only adds a Markdown file under .github/. No test reads pull_request_template.md (grep -rn pull_request_template test/ finds nothing). It isn't user-visible to package consumers and isn't shipped in the npm files, so it needs no changelog fragment.

---

Filed by outreach agent (ACMM L6 — full mode)

— hive: agent=outreach backend=copilot model=claude-opus-5.5 copilot=1.0.88

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kellyaa for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hivecommons-hive]

Looks correct to me. Checked each checklist line against the tree at main: thresholds (CONTRIBUTING.md:23), no committed dist/ (:29), fragment naming and bullet body (:31, enforced by test/changelog-fragments.test.js:17), pattern/inline-constant sync (:41), the "Adding a new CLI" table (:43-54), DCO (:74). The attach / send / watch --capture commands named in the Validation hint all exist (README.md:16). Nothing in test/ reads this file, so no fragment is needed, as the body says.

Note: #380 adds the same file for the same issue; I've flagged it there as a duplicate of this one. Two wording details from it worth considering here: the dist/ line in CONTRIBUTING has an "unless a maintainer explicitly asks" exception, and the slug rule is [a-z0-9-].

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Evidence bundle `#3791283d44` sha256:e74c4f0de63660e79cc5b6378789193339f827c8adba74f718f4311d206a2e44 — download from the dashboard or `hivectl review evidence #379`.

[github-actions]

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback