Spec Kit Bug Assessment
Independent PiSkill directory guide. The original prompt remains hosted by GitHub Spec Kit.
What does this prompt do?
Assesses a reported defect against repository evidence, expected behavior, reproduction details, impact, and implementation context before a fix is attempted.
Primary use case
Assess whether a bug report is reproducible and implementation-ready.
Expected output
A scoped defect assessment with evidence and open questions.
Inputs or variables
- bug report
- repository context
- reproduction evidence
Related prompts
Spec Kit Bug Fix
Turns an assessed defect into a bounded repair workflow that follows the repository plan, changes only relevant code, and captures validation evidence.
Trace Investigation
Uses logs, traces, timing, identifiers, and code paths to reconstruct a failing request or workflow and isolate the most likely root cause.
Behavior Reconstruction
Reconstructs actual software behavior from code paths, tests, logs, data, and interfaces when documentation is incomplete or a regression's expected state is unclear.
Issue Triage
Triages reported issues by reproducibility, impact, evidence, scope, dependencies, duplication, and next action so investigation effort goes to actionable defects first.
Azure DevOps Build Investigation
Collects Azure DevOps build information and organizes status, stages, failures, logs, and relevant repository context for efficient diagnosis.
Bug Investigation
Guides a focused investigation from symptoms through repository evidence to a defensible root-cause hypothesis.