singularity-forge/.github/PULL_REQUEST_TEMPLATE.md
Tom Boucher 7bad35702e chore: add PR template and bug report issue template (#574)
* chore: add PR template and bug report issue template

Standardize PR descriptions and bug reports with structured templates
to improve consistency across contributors.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* chore: simplify PR template — replace milestone/slice with target branch

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* chore: rename section to 'Release context'

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-15 19:47:20 -06:00

49 lines
1.5 KiB
Markdown

## Summary
<!-- What does this PR do? 1-3 bullet points. -->
-
## Motivation
<!-- Why is this change needed? Link issues if applicable. -->
Closes #
## Change type
<!-- Check one: -->
- [ ] `feat` — New feature or capability
- [ ] `fix` — Bug fix
- [ ] `refactor` — Code restructuring (no behavior change)
- [ ] `test` — Adding or updating tests
- [ ] `docs` — Documentation only
- [ ] `chore` — Build, CI, or tooling changes
## Scope
<!-- Which packages/areas does this touch? Check all that apply. -->
- [ ] `pi-tui` — Terminal UI
- [ ] `pi-ai` — AI/LLM layer
- [ ] `pi-agent-core` — Agent orchestration
- [ ] `pi-coding-agent` — Coding agent
- [ ] `gsd extension` — GSD workflow (`src/resources/extensions/gsd/`)
- [ ] `native` — Native bindings
- [ ] `ci/build` — Workflows, scripts, config
## Breaking changes
<!-- Does this change any public API, CLI behavior, config format, or file structure? -->
- [ ] No breaking changes
- [ ] Yes — describe below:
## Test plan
<!-- How was this tested? Check all that apply. -->
- [ ] Unit tests added/updated (`npm run test:unit`)
- [ ] Integration tests added/updated (`npm run test:integration`)
- [ ] Manual testing — describe steps:
- [ ] No tests needed — explain why:
## Rollback plan
<!-- If this causes issues in production, how do we revert safely? -->
- [ ] Safe to revert (no migrations, no state changes)
- [ ] Requires steps — describe:
## Release context
<!-- What branch does this PR target? -->
- **Target**: <!-- e.g., milestone/2.15.x or main -->