{"id":"a7ce8b2f-757c-471e-aa03-152a48aebcee","slug":"journey-06-feedback-skill-bug-report","kind":"skill","name":"Journey 06 — Feedback skill: bug report","summary":"Skill under test: prisma next feedback .","owner":"prisma","repoUrl":"https://github.com/prisma/prisma-next/blob/HEAD/skills/journey-tests/06-feedback-bug.md","license":"Apache-2.0","licenseTier":"permissive","trust":"official","stars":415,"match":null,"fewStars":false,"format":"instructions","createdAt":null,"addedAt":"2026-10-14T11:51:13.790Z","logoUrl":"https://avatars.githubusercontent.com/u/17219288?v=4","linkOnly":false,"collection":{"name":"prisma-next","repo":"prisma/prisma-next"},"skillPath":"skills/journey-tests/06-feedback-bug.md","categories":["developer-tools"],"tags":["loggy-core","loggy-terminal"],"runtime":"binary","local":true,"cloudCapable":false,"cloudCapability":"unknown","cloudReadyOnPlatform":false,"needsApiKey":false,"reviewed":false,"syncedAt":"2026-10-14T11:51:13.786Z","sample":false,"url":"https://conduits.dev/tools/journey-06-feedback-skill-bug-report","language":"TypeScript","transports":[],"install":{},"requirements":{"env":[],"upstreamMayCharge":false},"tools":null,"readme":"# Journey 06 — Feedback skill: bug report\n\n**Skill under test:** `prisma-next-feedback`.\n\n**Acceptance criterion:** AC8c (bug report path) from `specs/usage-skill.spec.md`.\n\n## Setup\n\nA `prisma-next init`-scaffolded project (any target).\n\n## Prompt\n\n> I want to report that `prisma-next migration plan` exits 0 even when the planner found no diff — that's surprising\n\n## Expected agent behaviour\n\n- [ ] Skill matcher fires on `prisma-next-feedback`.\n- [ ] Agent classifies as a **bug report** (the CLI exit code is arguably wrong vs. documented behaviour). Not a feature request.\n- [ ] Agent produces a minimal reproduction:\n  - A small `schema.psl` excerpt (renamed to neutral domain names like `User`, `Post`).\n  - The exact command (`prisma-next migration plan --name no-op`) and its full output.\n  - A numbered list of steps to reproduce.\n- [ ] Agent collects the environment block:\n  - Prisma Next version (from `pnpm ls @prisma-next/postgres` or similar).\n  - Node version (`node -v`).\n  - Package manager + version.\n  - OS.\n- [ ] Agent renders the issue body using the bug-report fields from `.github/ISSUE_TEMPLATE/bug_report.yml`: *Package and version / What happened? / What did you expect to happen? / Minimal reproduction / Environment / Additional context*.\n- [ ] Agent renders a conventional-commit title: `bug(cli): migration plan exits 0 when there is no diff`.\n- [ ] Agent surfaces the rendered title + body to the user for confirmation **before** submitting.\n- [ ] On user confirmation, agent submits via `gh issue create` (preferred) or opens the prefilled new-issue URL in the browser.\n- [ ] Agent records the issue URL in the user's project notes.\n\n## Success criteria\n\n- [ ] No `DATABASE_URL` strings or secrets in the body.\n- [ ] No customer-domain model names in the body.\n- [ ] Body contains all required fields named in the bug-report issue form (`Package and version`, `What happened?`, `What did you expect to happen?`, `Minimal reproduction`, `Environment`).\n- [ ] Title is in conventional-commit form.\n- [ ] User was prompted for confirmation before submission.\n- [ ] Issue submitted to `prisma/prisma-next` (verified by URL in the agent's response)."}