Create a Bug
Turn symptoms, logs, or an observed regression into a bug that another engineer can reproduce and fix without guessing.
Workflow
- Identify the target repository and issue provider from the request, repository remote, or available provider tools. If no writable provider is available, produce a provider-neutral Markdown draft.
- Search open and closed issues for the behavior, component, and distinctive error text. Link a real duplicate instead of creating another issue.
- Inspect the relevant code, tests, configuration, and recent changes. Separate observed evidence from hypotheses.
- Reproduce the bug when it is safe and practical. Record the smallest deterministic steps, inputs, environment, actual result, and expected result. Never claim a reproduction you did not run.
- Scope impact: affected users or workflows, severity, regression status, workaround, and data/security risk. Mark unknowns explicitly.
- Require a regression test that fails before the fix and passes after it. Name the appropriate test layer and fixture when repository evidence supports it.
- Draft the bug using the template below. Show the final draft before creating or mutating an external ticket unless the user already explicitly authorized creation.
- Create the issue with the native provider capability when available, then return its URL. Otherwise return the complete Markdown draft and the missing provider action.
Bug template
## Summary
<one sentence naming the broken behavior and affected user>
## Reproduction
1. <minimal deterministic step>
2. <next step>
3. <observed result>
## Expected behavior
<what should happen, grounded in a requirement, test, or established behavior>
## Actual behavior
<what happens, including exact error text where useful>
## Impact
<who is affected, severity, frequency, workaround, regression status>
## Evidence
- <code path, test, log, screenshot, revision, or linked issue>
## Regression test
- [ ] <specific test that fails before the fix and passes after it>
## Environment
- Version/revision:
- OS/runtime/browser:
- Configuration:
## Open questions
- <only unresolved facts that could change scope or severity>
Safety rules
- Do not paste access tokens, credentials, personal data, or unnecessary customer content into a public issue.
- Redact secrets in logs while preserving useful error structure.
- Do not turn a suspected cause into a fact without evidence.
- Do not implement the fix, commit, push, or change issue state unless the user asks.
Built by aictrl.dev. This skill teaches the workflow; aictrl operationalizes it — grounded in your backlog, team standards, and codebase knowledge graph. See how →
1---2name: create-bug3description: Create an evidence-backed bug report with reproduction, expected and actual behavior, impact, code context, and a regression-test requirement. Use when the user says "file a bug", "report this defect", "turn these symptoms into a ticket", or describes broken or regressed behavior.4---56# Create a Bug78Turn symptoms, logs, or an observed regression into a bug that another engineer can reproduce and fix without guessing.910## Workflow11121. Identify the target repository and issue provider from the request, repository remote, or available provider tools. If no writable provider is available, produce a provider-neutral Markdown draft.132. Search open and closed issues for the behavior, component, and distinctive error text. Link a real duplicate instead of creating another issue.143. Inspect the relevant code, tests, configuration, and recent changes. Separate observed evidence from hypotheses.154. Reproduce the bug when it is safe and practical. Record the smallest deterministic steps, inputs, environment, actual result, and expected result. Never claim a reproduction you did not run.165. Scope impact: affected users or workflows, severity, regression status, workaround, and data/security risk. Mark unknowns explicitly.176. Require a regression test that fails before the fix and passes after it. Name the appropriate test layer and fixture when repository evidence supports it.187. Draft the bug using the template below. Show the final draft before creating or mutating an external ticket unless the user already explicitly authorized creation.198. Create the issue with the native provider capability when available, then return its URL. Otherwise return the complete Markdown draft and the missing provider action.2021## Bug template2223```markdown24## Summary25<one sentence naming the broken behavior and affected user>2627## Reproduction281. <minimal deterministic step>292. <next step>303. <observed result>3132## Expected behavior33<what should happen, grounded in a requirement, test, or established behavior>3435## Actual behavior36<what happens, including exact error text where useful>3738## Impact39<who is affected, severity, frequency, workaround, regression status>4041## Evidence42- <code path, test, log, screenshot, revision, or linked issue>4344## Regression test45- [ ] <specific test that fails before the fix and passes after it>4647## Environment48- Version/revision:49- OS/runtime/browser:50- Configuration:5152## Open questions53- <only unresolved facts that could change scope or severity>54```5556## Safety rules5758- Do not paste access tokens, credentials, personal data, or unnecessary customer content into a public issue.59- Redact secrets in logs while preserving useful error structure.60- Do not turn a suspected cause into a fact without evidence.61- Do not implement the fix, commit, push, or change issue state unless the user asks.6263---64**Built by [aictrl.dev](https://aictrl.dev/?utm_source=oss-skills&utm_medium=skill&utm_campaign=create-bug&utm_listing=github-skills&utm_platform=portable&utm_skill=create-bug).** This skill teaches the workflow; aictrl *operationalizes* it — grounded in your backlog, team standards, and codebase knowledge graph. [See how →](https://aictrl.dev/features?utm_source=oss-skills&utm_medium=skill&utm_campaign=create-bug&utm_listing=github-skills&utm_platform=portable&utm_skill=create-bug)
aictrl-dev