Add GitHub issue templates and a PR template that capture environment + `doctor --bundle`

[hojinzs]

Problem

The repo has no .github/ISSUE_TEMPLATE/ and no PULL_REQUEST_TEMPLATE.md (find .github -type f returns only workflows/ci.yml and workflows/release.yml). Yet the README markets gh-symphony doctor --bundle as the bug-report mechanism (README.md:337, 368-380), and the project already has conventions in PROJECT_MANAGE.md:33-47 (Background / Proposed Changes / Affected Files) and PR expectations in CONTRIBUTING.md — none wired into GitHub-native templates. README does not even link to those docs, so a human filing via the GitHub UI gets a blank box.

Impact (OSS user)

With zero open issues, a new user hitting an onboarding failure has no structured way to report it, and maintainers receive low-context reports without OS/Node/install-method/runtime or the recommended support bundle. PRs arrive without the documented checklist.

Evidence (real files)

• .github/ contains only workflows/.
• README.md:337, 368-380 (doctor --bundle); packages/cli/src/support/bundle.ts builds it; packages/cli/src/commands/doctor.ts handles --bundle/--json.
• PROJECT_MANAGE.md:33-47; CONTRIBUTING.md:18-23.

Proposed fix

Add .github/ISSUE_TEMPLATE/bug_report.yml (ask for OS, Node version, install method npm/docker, chosen runtime, gh-symphony doctor --json output, and an attached gh-symphony doctor --bundle) and feature_request.yml mirroring PROJECT_MANAGE.md's sections, plus .github/PULL_REQUEST_TEMPLATE.md mirroring CONTRIBUTING.md's checklist. Optionally a config.yml linking Discussions/CONTRIBUTING.

---

Priority: P1 · Symphony layer: DX/Meta · category: community-health
Filed from an OSS-user-perspective audit of the repo.

[moncher-dev]

요구사항 확인 결과, PROJECT_MANAGER.md가 아니라 현재 repo에는 PROJECT_MANAGE.md가 있고, 여기의 Issue Template 가이드는 그대로 버리기보다 GitHub native template의 공통 구조로 쓰는 게 맞아 보입니다.

권장 방향:

1. PROJECT_MANAGE.md의 공통 섹션은 유지/반영

   • Background
   • Proposed Changes
   • Affected Files
   • 필요 시 Spec Reference, Migration Notes, Symptoms / Reproduction Steps, References

2. 다만 bug_report.yml은 위 공통 구조만으로는 부족하므로, 이 이슈의 핵심인 support bundle 중심 필드를 추가

   • OS
   • Node version
   • install method: npm / docker / other
   • chosen runtime
   • gh-symphony doctor --json output
   • gh-symphony doctor --bundle attachment 안내
   • reproduction steps / expected vs actual behavior

3. feature_request.yml은 PROJECT_MANAGE.md의 구조를 거의 그대로 issue form화

   • Background
   • Proposed Changes
   • Affected Files
   • References / spec links optional

4. .github/PULL_REQUEST_TEMPLATE.md는 CONTRIBUTING.md의 PR expectations와 required checks를 checklist로 반영

   • linked issue
   • user-visible behavior / operational impact
   • screenshots or terminal output when UX/deployment changes
   • pnpm lint, pnpm test, pnpm typecheck, pnpm build, pnpm format
   • Changeset 여부
   • follow-up work

5. 가능하면 .github/ISSUE_TEMPLATE/config.yml도 추가

   • CONTRIBUTING.md, SECURITY.md, support/doctor bundle 안내 링크
   • blank issue 허용 여부는 maintainer 판단에 맡김

Acceptance criteria 제안:

• .github/ISSUE_TEMPLATE/bug_report.yml이 추가되어 GitHub UI에서 Bug Report form으로 보인다.
• Bug Report form은 environment, install/runtime 정보, doctor --json, doctor --bundle 첨부를 명시적으로 요청한다.
• .github/ISSUE_TEMPLATE/feature_request.yml이 추가되어 PROJECT_MANAGE.md의 Background / Proposed Changes / Affected Files 구조를 따른다.
• .github/PULL_REQUEST_TEMPLATE.md가 추가되어 CONTRIBUTING.md의 PR checklist와 validation commands를 반영한다.
• README 또는 issue template config에서 bug report / contributing / support bundle 경로를 찾을 수 있다.
• 기존 .github/workflows/ci.yml, .github/workflows/release.yml은 불필요하게 변경하지 않는다.

따라서 구현자는 PROJECT_MANAGE.md를 기준 문서로 삼되, bug report는 doctor --bundle 기반 OSS support workflow에 맞춰 별도 form으로 확장하는 방향을 추천합니다.

[moncher-dev]

Workpad — #391 — Cycle 1

Type: fresh pickup
Branch: feat/391-github-templates
Draft PR: #423 (ready for review)
Cycle opened: 2026-07-02T04:25:07Z · Trigger: Fresh Ready pickup for GitHub issue/PR templates

Status Transitions

• 2026-07-02T04:29:57Z · Ready → In progress · Draft PR opened and implementation branch ready (cycle 1 open)
• 2026-07-02T04:30:56Z · In progress → In review · Completion Bar passed and PR Add GitHub issue and PR templates #423 handed off for review (cycle 1 close)

Plan

• 1. Add GitHub issue forms and PR template aligned with doctor bundle and repo contribution conventions
• 2. 마무리: 원본 이슈 재검증 · Completion Bar 통과 · changeset (필요 시) · PR ready · In review 전이

Rework / PR Feedback

• N/A — fresh pickup; no open linked PR with actionable review feedback.

Completion Bar

• In-scope requirements implemented
• pnpm lint
• pnpm test
• pnpm typecheck
• pnpm build
• Docker E2E (if integration behavior changed) — N/A, GitHub metadata only; no integration behavior changed
• Tests for new functionality (or justified N/A) — YAML parse and targeted Prettier checks cover template validity; no runtime code path added
• Code conventions (CLAUDE.md)
• Inline review comments answered (rework only) — N/A, fresh cycle

Validation

• ruby -e 'require "yaml"; ARGV.each { |f| YAML.load_file(f); puts "ok #{f}" }' .github/ISSUE_TEMPLATE/bug_report.yml .github/ISSUE_TEMPLATE/feature_request.yml .github/ISSUE_TEMPLATE/config.yml — pass
• pnpm exec prettier --check .github/ISSUE_TEMPLATE/bug_report.yml .github/ISSUE_TEMPLATE/feature_request.yml .github/ISSUE_TEMPLATE/config.yml .github/PULL_REQUEST_TEMPLATE.md — pass
• pnpm lint — pass
• pnpm test — pass
• pnpm typecheck — pass
• pnpm build — pass
• pnpm format — fail due pre-existing repository-wide formatting drift outside this PR; targeted changed files pass Prettier
• Changeset: N/A (no release-package behavior change; labels do not request a changeset)
• Docker E2E evidence: N/A (GitHub metadata only)
• Merge commit (Land cycle only): N/A

위임 (out-of-scope / human / post-merge)

• Confirm GitHub renders the issue forms and PR template as intended in the web UI.

Progress Log

• 2026-07-02T04:25:07Z: Classified work as Integration Layer DX/Meta; confirmed issue is actionable and no open linked PR requires rework.
• 2026-07-02T04:29:57Z: Added GitHub bug report, feature request, issue-template config, and PR template; pushed branch and opened draft PR Add GitHub issue and PR templates #423.
• 2026-07-02T04:30:56Z: Re-read issue requirements, confirmed spec conformance/no upstream spec divergence, marked PR Add GitHub issue and PR templates #423 ready, and moved issue to In review.

Blockers

None

[moncher-dev]

🔁 Status: Ready → In progress

Reason: Branch prepared and Cycle 1 implementation resumed for GitHub issue/PR templates
Cycle: 1 open

[moncher-dev]

🔁 Status: Ready → In progress

Reason: Draft PR opened and implementation branch ready
Cycle: 1 open