bug-report

Structure comprehensive bug reports with reproduction steps, environment details, severity assessment, and git bisect guidance.

Installation

Copy this skill directory into your Mayros skills folder:

cp -r skills/bug-report ~/.mayros/skills/bug-report

Or install via the Skills Hub:

mayros skill install @apilium/bug-report

Usage

Activate the skill and describe the bug:

Create a bug report: the login page crashes when clicking submit with an empty email field

The skill structures the report with:

• Title -- concise description
• Environment -- OS, runtime, app version, device
• Steps to reproduce -- numbered, minimal, deterministic
• Expected vs actual behavior
• Severity -- Critical (P0), High (P1), Medium (P2), Low (P3)
• Frequency -- always, sometimes, rarely, once
• Workaround -- if any temporary fix exists

Severity Assessment

| Level | Criteria | Response Time | |-------|----------|--------------| | Critical (P0) | Data loss, security breach, complete outage, no workaround | Hours | | High (P1) | Major feature broken, significant user impact | 1-2 days | | Medium (P2) | Partial functionality loss, workaround available | Next sprint | | Low (P3) | Cosmetic, edge case, easy workaround | Backlog |

Regressions are automatically bumped to at least High severity.

Git Bisect

For regressions, the skill guides you through git bisect:

git bisect start
git bisect bad                # current commit is broken
git bisect good v1.0.0        # last known working version
# Test each commit git checks out, then:
git bisect good               # if it works
git bisect bad                # if it is broken
git bisect reset              # when done

Automated bisect with a test script:

git bisect start
git bisect bad HEAD
git bisect good v1.0.0
git bisect run npm test

Completeness Scoring

The skill assesses report completeness by checking for:

• Title / summary
• Environment details (OS, runtime, version)
• Steps to reproduce
• Expected behavior
• Actual behavior
• Severity classification

Reports missing fields receive a lower completeness score with specific guidance on what to add.

Semantic Predicates

| Predicate | Description | |-----------|-------------| | bug:report_created | A structured bug report was produced | | bug:severity_assessed | Severity was determined for a report | | bug:report_context | Namespace-level bug report history |

License

MIT