Files triaged bug reports as local markdown folders with screenshots and an HTML tracker.
npx skills add https://github.com/cagriy/dev-skills --skill bug-submit-cagriy
Please help me install this Agent Skill. Skill: bug-submit Source: https://github.com/cagriy/dev-skills/tree/main/skills/bug-submit Command: npx skills add https://github.com/cagriy/dev-skills --skill bug-submit-cagriy
bugs/bug-N-<slug>/ folder with a markdown report containing description, reproduction steps, severity, and a triage section grounded in a quick read of the relevant code paths. - Screenshot attachment handling: Copies images pasted into the conversation or passed as paths into the bug folder and links them relatively in the report, with a confirmation gate for potentially sensitive files. - Automatic tracker generation: Regenerates a repo-wide bugs/bugs-tracker.html Issues view listing open and archived bugs via the delegated bug-tracker-render skill. - Use Case: While testing your app you notice the login button does nothing on Safari. Describe it in one sentence, paste a screenshot, and the skill files bugs/bug-4-login-button-does-nothing-on-safari/ with a triaged report and updates the tracker. ## Quick Start Ask the assistant to file a bug report describing what broke, what you expected, and attach any screenshots of the problem.High-intent search queries and answers about installing and using this skill.
Describe the bug in chat or invoke /bug-submit with a description and optional image paths. The skill creates a bugs/bug-N-slug/ folder containing a markdown report with description, severity, and triage, then updates the HTML tracker.
Paste images directly into the chat or pass image file paths as arguments. The skill detects paths surfaced via [Image: source: path] annotations, validates them, and copies the files into the bug folder with relative links in the report.
No. Everything stays local under the repository's bugs/ directory. The skill never creates GitHub issues, commits, pushes, or uploads images anywhere; it only writes the bug folder and regenerates the local HTML tracker.
The skill scans both bugs/ and bugs/archive/ for existing bug-N folders, takes the numeric maximum, and adds one. Scanning the archive ensures numbers are never reused after a resolved bug is moved out of the active folder.
The skill pauses and asks one clarifying chat message requesting a proper description and screenshots before creating anything. If you still provide nothing substantive, it stops cleanly with no folder or files created.
Yes. Images that look sensitive require an explicit 'proceed' confirmation before being copied into the repo, and any credentials detected in the description are redacted from the report with a warning before writing.
softmgGuide Codex to reproduce local browser scenarios and capture evidence.
bzellmanAutomate end-to-end bug-to-PR workflows from triage to deployment.
AbildtoftAnalyze code diffs to detect bugs, security issues, and quality risks.
carson-sweetImport open GitHub issues into local Markdown story files.