add-bug
Skill0 starsChanged 5 months agoMITView on GitHub
Add a bug report to docs/bugs.md with timestamp, description, and status tracking. Use when the user wants to log a bug they've found.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- remotion-dev/remotiontheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- remotion-dev/remotion★ 73ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- add-featureSkill
- fix-bugSkill
- list-bugsSkill
- review-my-codeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 78
Use the <TIMEZONE> timezone for timestamps
- Distinctive: line 79
Keep the short title under 60 characters
- Distinctive: line 80
If the user provides multiple bugs in one message, create a separate entry for each
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Bug Report
Log a bug to docs/bugs.md with structured metadata for future tracking and automated fixing.
Process
- Get bug details — The user will describe the bug either as arguments to the command or in their message. If no description is provided, ask for one using AskUserQuestion.
- Read the current file — Read
docs/bugs.mdto understand the current content and find the right place to append. - Generate the entry — Create a new bug entry using this format:
### BUG-{NNN}: {Short title}
| Field | Value |
|-------|-------|
| **Status** | 🔴 Reported |
| **Reported** | {YYYY-MM-DD HH:MM <TIMEZONE>} |
| **Severity** | {Critical / High / Medium / Low} |
| **Area** | {<area-1> / <area-2> / <area-3>} |
**Description:**
{Detailed description of the bug}
**Steps to reproduce:**
{Steps if provided, otherwise "Not yet documented"}
**Expected vs actual:**
{If provided, otherwise "Not yet documented"}
---- Assign the bug number — Look at existing entries in
docs/bugs.mdand increment from the highestBUG-NNNnumber found. If no entries exist, start atBUG-001. - Determine severity — If the user doesn't specify severity, infer from the description:
- Critical: Data loss, security issue, payments broken, app crash
- High: Core feature broken, blocking users
- Medium: Feature partially broken, workaround exists
- Low: Cosmetic, minor UX issue, edge case
- Determine area — Infer from the bug description which part of the system is affected (one of your configured areas — see Configuration). If unclear, ask.
- Append the entry — Add the new bug entry to the end of
docs/bugs.md. - Confirm — Tell the user the bug has been logged with its ID, e.g. "Logged as BUG-003 (Medium,
<area-1>)".
Status lifecycle
These are the valid statuses — only Reported is used by this skill. Other statuses are for reference when bugs are triaged or fixed later:
| Status | Meaning |
| 🔴 Reported | Newly logged, not yet investigated |
| 🟡 Confirmed | Reproduced and validated |
| 🔵 In Progress | Actively being fixed |
| 🟢 Fixed | Fix applied and verified |
| ⚪ Won't Fix | Intentional or out of scope |
Configuration
Replace these placeholders with your project's values before using the skill:
<area-1> / <area-2> / <area-3>— the modules / sub-projects in your repo used to tag bugs (e.g.frontend / backend / api / mobile / infra). Edit the Area field in the template and step 6. Keep this list identical acrossadd-bug,list-bugs, andfix-bug.<TIMEZONE>— the timezone for timestamps (e.g.UTC,America/New_York,Europe/London). Edit the Reported field.
See the repository README for the full placeholder reference shared across skills.
Notes
- Use the
<TIMEZONE>timezone for timestamps - Keep the short title under 60 characters
- If the user provides multiple bugs in one message, create a separate entry for each
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

