Drafts and iterates structured bugreport.md files for local development defects.
npx skills add https://github.com/FHIR/fhir-codegen --skill dev-report-fhir
Please help me install this Agent Skill. Skill: dev-report Source: https://github.com/FHIR/fhir-codegen/tree/main/.github/skills/dev-report Command: npx skills add https://github.com/FHIR/fhir-codegen --skill dev-report-fhir
bugreport.md with symptoms, repro steps, ranked hypotheses, and blast radius. ## Core Features & Use Cases - Structured bug reports: Produces a bugreport.md with fixed sections (Summary, Environment, Symptoms, Steps to Reproduce, Evidence, Hypotheses, Workarounds, Blast Radius, Open Questions) under a gitignored scratch/ directory. - Slot-based targeting: Accepts a full file path or a short slot number that expands to scratch/<MMDD>-<##>/bugreport.md using today's date. - GitHub issue seeding: Optionally fetches an existing issue via gh issue view to seed the draft title, summary, and notes. - Interactive open-questions walkthrough: Offers a one-question-at-a-time walkthrough with recommended answers to close gaps in the report. - Use Case: You hit a failing code-generation test in the fhir-codegen repo. Run the Skill with slot 3 and paste the stack trace; it creates scratch/0423-03/bugreport.md, ranks likely root causes, and walks you through the missing environment details. ## Quick Start Ask the assistant to draft a bug report for slot 3 using the error message and stack trace you paste in.High-intent search queries and answers about installing and using this skill.
Provide a target file path or slot number plus your raw description of the defect, such as an error message or log excerpt. The Skill writes a bugreport.md with sections for symptoms, repro steps, evidence, hypotheses, workarounds, and blast radius.
Pass an issue reference as #N, gh#N, or a full issue URL along with the target. The Skill fetches it with gh issue view and uses the title for the heading, the body for the summary, and labels and URL for notes.
Yes. If the resolved bugreport.md already exists, the Skill reads the current content and revises it based on your new input, preserving sections you have not asked to change. Providing only a target opens the file for review.
No. It stays in a Tech Lead role: it may open referenced files to refine hypotheses, but it never edits code, runs full test suites, or commits. Fixes belong to the separate dev-do skill and plans to dev-plan.
Reports live under the scratch/ directory, which is gitignored, in slots named scratch/<MMDD>-<##>/bugreport.md. They are local working documents and are never committed to the repository.
kamelmhAnalyze error messages, stack traces, and logs to isolate root causes.
ContentsUSExecute implementation plans from GitHub issues into pull requests.
GinoCanessaGenerates three isolated solution designs and a judged selection from a feature request or bug report.
hero-engineFrames quality work as shared product responsibility with clear QA expertise and accountable handoffs.