Automated summary
Writes Markdown bug reports into DevPlans/Bugs/ following a status-prefixed naming convention (OPEN-, FIXED-, REJECTED-) and a fixed set of sections.
Strengths
- Enforces a consistent template (summary, symptoms, root cause, affected code, solutions, priority) so reports stay comparable
- Status prefix in the filename makes each bug's state visible at a glance
- Requires listing affected files with line numbers plus alternative solutions
- Explicitly covers renaming the file when a bug is fixed or rejected
Limitations
- Assumes a DevPlans/Bugs/ directory already exists and the team follows the same convention
- Provides no search, filtering, or aggregate tracking beyond the Markdown files themselves
- Root Cause and Potential Solutions sections depend on details the user has to supply
Use when a user asks to create, log, file, or report a bug and wants a structured report stored in the repo.
Avoid when the project tracks bugs in an external system like GitHub Issues or Jira, or uses a different directory layout.
Security analysis
SafeThe skill only uses Write, Read, and Glob to create and manage markdown bug report files under DevPlans/Bugs/. It does not execute shell commands, access network resources, exfiltrate data, or perform destructive actions.
No concerns found
How this analysis is madeExamples
Create a bug report for the slow chunk rendering — frames drop to 4 FPS when more than 200 chunks are loaded. Include the profiler output and point at TerrainRenderer.cs.Log a bug: the app crashes on startup when config.json has a trailing comma. Affected code is in ConfigLoader.cs around line 88.The bug in OPEN-SlowChunkRendering.md is resolved now, rename it to FIXED and note the fix in the solutions section.name: bug-report description: Log a bug report. Use when user asks to create, log, file, or report a bug. allowed-tools: Write, Read, Glob
Bug Report Skill
Create bug reports in DevPlans/Bugs/ following the project's bug tracking conventions.
File Naming
{STATUS}-{BugName}.md
| Status | Meaning | |--------|---------| | OPEN | Active bug, not yet fixed | | FIXED | Bug has been resolved | | REJECTED | Not a bug, or won't fix |
New bugs should always start with OPEN-.
Required Sections
# Bug: {Title}
## Summary
Brief description of the issue.
## Symptoms
- Observable behaviors
- Error messages
- Performance impacts
## Root Cause
Technical explanation of why this happens (if known).
## Affected Code
- List relevant files and line numbers
- `path/to/file.cs:123`
## Potential Solutions
### 1. Solution Name
Description of approach, tradeoffs.
### 2. Alternative
Another option if applicable.
## Priority
Low / Medium / High / Critical
## Related Files
- `path/to/related/file.cs`
Example
For a bug about slow rendering:
- File:
DevPlans/Bugs/OPEN-SlowChunkRendering.md - Title:
# Bug: Slow Chunk Rendering - Include profiling data if available
Status Changes
When a bug is fixed or rejected, rename the file:
OPEN-MyBug.md→FIXED-MyBug.mdOPEN-MyBug.md→REJECTED-MyBug.md
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/bug-report-mmio7147/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/bug-report-mmio7147' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/bug-report-mmio7147/download' --output '.skill-downloads/bug-report-mmio7147/SKILL.md.part' && mv '.skill-downloads/bug-report-mmio7147/SKILL.md.part' '.skill-downloads/bug-report-mmio7147/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Write, Read, Glob
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/bug-report-mmio7147/SKILL.md' && test -s '.skill-downloads/bug-report-mmio7147/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/bug-report' && cp -R '.skill-downloads/bug-report-mmio7147' '.claude/skills/bug-report'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/bug-report-mmio7147'openskills read 'bug-report-mmio7147'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/bug-report-mmio7147/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.