grimoire-bug-explore

Analyze feature specs and code to identify untested paths and coverage gaps.

Updated Jan 26, 2025
One-click install
npx skills add https://github.com/jlissner/lissner.io --skill grimoire-bug-explore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grimoire-bug-explore
Source: https://github.com/jlissner/lissner.io/tree/main/.claude/skills/grimoire-bug-explore
Command: npx skills add https://github.com/jlissner/lissner.io --skill grimoire-bug-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-guided exploratory testing that systematically identifies gaps in feature coverage, generates edge-case scenarios, and surfaces untested paths to prevent bugs before users encounter them.

Core Features & Use Cases

  • Gap analysis across feature specs and code to reveal missing coverage and risky areas.
  • Automatic generation of negative scenarios and edge cases from existing scenarios.
  • Modes including Tester, Developer, and Onboard to tailor the depth of analysis and onboarding guidance.

Quick Start

Begin a time-bounded grimoire-bug session to discover untested paths and gaps.

Frequently Asked Questions about grimoire-bug-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find untested paths and gaps in my test coverage?

To find untested paths, exploratory testing analyzes feature specs, code, and existing automation to surface coverage gaps. It targets exploration across recent changes or full sweeps, generating negative scenarios and risk insights for actionable next steps.

What is exploratory testing for negative scenarios and edge cases?

Exploratory testing for negative scenarios is an AI-guided method to systematically identify risky edge cases. It automatically generates untested paths and negative scenarios from existing automation, revealing gaps in feature coverage before users encounter bugs.

How do I generate edge cases from existing test automation?

You generate edge cases from test automation by running a bug-hunting analysis that reviews current tests and feature specs. This surfaces automation gaps and produces structured negative scenarios prioritized by risk for immediate follow-up.

Can I tailor exploratory testing depth for developers versus testers?

Yes, you can tailor exploratory testing depth using Tester, Developer, and Onboard modes. These modes adjust the depth of gap analysis and onboarding guidance to match the specific needs of developers or testers exploring feature coverage.

What is the best way to prioritize risk analysis for missing test coverage?

The best way to prioritize risk analysis is to use AI-guided exploration that surfaces untested paths and enforces structured outputs. This generates risk prioritization and actionable next steps based on the severity of discovered automation gaps.

When should I use AI-guided bug hunting instead of manual test sweeps?

You should use AI-guided bug hunting when you need to systematically uncover gaps across large scopes like recent changes or full sweeps. It accelerates discovery by automatically generating negative scenarios and risk insights that manual sweeps might miss.