Create bug

Skill aictrl-dev/skills/skills/create-bug

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.From its SKILL.md

Install

npx -y skills add aictrl-dev/skills --skill create-bug

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.3 KB, 633 tokens by cl100k_base, as published. Nobody here has run it

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 →

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most bug reports skills give in 633 tokens

Counted across 130 of the 155 authors here whose files we hold, read 2026-09-06

Reproduce the bug as a new failing regression test firstin 11 of 130, across 4 files
Add security-reviewer for security-sensitive defectsin 10 of 130, across 3 files
Skip the research phase by defaultin 10 of 130, across 3 files
Escalate build breaks to build-error-resolverin 10 of 130, across 3 files
Stop at Gate 1 and Gate 2in 10 of 130, across 3 files
Fix until that test goes greenin 10 of 130, across 3 files
Run the orch-pipeline engine with the settings abovein 10 of 130, across 3 files
Scope unclear root causes with code-explorer before writing the red testin 10 of 130, across 3 files
Replace sensitive data with placeholdersin 6 of 130, across 3 files
Match severity rating to actual impactin 6 of 130, across 3 files
Reference screenshots and attachments inlinein 6 of 130, across 3 files
Create issues as markdown filesin 5 of 130, across 2 files

Said here and by no other author read

Link a real duplicate instead of creating another issue
Separate observed evidence from hypotheses
Reproduce the bug when safe and practical
Record the smallest deterministic reproduction steps and expected result
Scope impact and mark unknowns explicitly
Draft the bug using the template

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.