Structured bug reporting for testers. Guides creation of reproducible, context-rich bug reports that link to existing feature specs. Accepts output from testing tools (Playwright, Cypress, etc.) via MCP or directly. Use when a tester or non-developer needs to file a bug.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "grimoire-bug-report" with this command: npx skills add jlissner/skillsmp-jlissner-jlissner-grimoire-bug-report
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Triage bug reports — classify the root cause, route to the right team (code, infra, config, data, third-party, docs), and communicate decisions back. Reads from local reports or external tickets via MCP. Use when picking up a bug report.
Generate area docs and data schema from a codebase snapshot. Use when initializing grimoire on an existing project or when codebase structure has changed significantly.
Systematically find, prioritize, and plan tech debt reduction. Use when the user wants to identify and address code quality issues, complexity, or duplication.
Implement tasks from a planned grimoire change with strict red-green BDD. Use when tasks.md exists and is ready for implementation.