Investigate and fix a bug
Turn a vague failure into a reproducible case and a focused regression fix.
AI working habits
Investigate a reported software defect and verify a minimal correction when a concrete failure or regression is supplied.
This original, instruction-only skill helps with a specific repeatable decision process. It does not install tools or run background jobs.
Investigate a reported software defect and verify a minimal correction when a concrete failure or regression is supplied.
Read the complete skill before saving it in a project-local skill folder. Select the appropriate tool above for the documented discovery path. Keep durable project facts in the repository’s own instructions and use this skill when its described task applies.
The text is MIT licensed. Compatibility here means the documented SKILL.md format and folder location were reviewed; Pristren has not performed a live run through each coding tool. Judge the result using the workflow’s acceptance checks.
Tool setup checked against official documentation. Pristren has not executed this workflow through this tool.
Create the project-local skill directory
mkdir -p .agents/skills/reproduce-before-fixCommand reference--- name: reproduce-before-fix description: Investigate a reported software defect and verify a minimal correction when a concrete failure or regression is supplied. --- # Reproduce before fixing Convert the reported symptom into a repeatable input and expected behavior. Record the environment and the exact observable failure. If a safe reproduction is unavailable, state the limitation and inspect the relevant path before changing behavior. Trace the failing input through its call path. Identify the first point where observed behavior departs from the intended contract. Treat logs, tests, and source as evidence; do not assume the most recent edit caused the defect. Choose the smallest change that corrects the demonstrated cause. Preserve unrelated behavior and human edits. Add a regression check when it captures a meaningful boundary or the failure is likely to return. Avoid a test that only asserts the current implementation's wording or internal structure. Run the reproduction against the correction. Exercise the nearest relevant edge case, then the existing checks appropriate to the affected area. If a check fails for a separate reason, distinguish that failure and retain its evidence instead of suppressing it. Report the trigger, cause, resulting behavior, verification, and any unresolved limitation. Do not claim that a defect is fixed solely because a patch compiles.
License and access: MIT for this Pristren-authored prompt or instruction text.
Turn a vague failure into a reproducible case and a focused regression fix.
Deliver one complete user journey with honest state handling and useful verification.