From grace
Debugs issues in GRACE-structured projects via semantic navigation of knowledge graphs, verification plans, and blocks to analyze mismatches and apply targeted fixes.
npx claudepluginhub osovv/grace-marketplace --plugin graceThis skill uses the workspace's default tool permissions.
Debug an issue using GRACE semantic navigation.
Fixes bugs via root cause diagnosis with debugger/gap-analyzer, requirements.md generation, /execute delegation, 3-retry circuit breaker, and QA.
Use when investigating bugs, errors, failing tests, or unexpected behavior. Enforces systematic root-cause investigation BEFORE attempting any fix. Invoke this skill before writing any fix code.
Executes hypothesis-driven debugging workflow: triage and reproduce bugs, investigate with evidence, analyze root causes, fix and verify, then report. For 'fix this bug' or debug requests.
Share bugs, ideas, or general feedback.
Debug an issue using GRACE semantic navigation.
From the error/description, identify which module is likely involved:
docs/knowledge-graph.xml for module overviewdocs/verification-plan.xml for relevant scenarios, test files, or log markers if availabledocs/operational-packets.xml for the canonical FailurePacket shape if availableIf the optional grace CLI is available, you may use:
grace module find <query> --path <project-root> to resolve likely module IDs from stack traces, paths, verification refs, or dependency namesgrace module show M-XXX --path <project-root> --with verification to pull the shared/public module and verification snapshotgrace file show <path> --path <project-root> --contracts --blocks when you already know the governed file and need its local/private navigation surfaceIf the error contains a log reference like [Module][function][BLOCK_NAME]:
START_BLOCK_BLOCK_NAME in the codebase — this is the exact locationIf the failure came from a named verification scenario or test:
V-M-xxx entry in docs/verification-plan.xmlIf no log reference:
Read the identified block, its CONTRACT, and relevant verification entry. Determine:
Apply the fix WITHIN the semantic block boundaries. Do NOT restructure blocks unless the fix requires it.
After fixing:
docs/verification-plan.xml$grace-verification to strengthen automated checks before considering the issue fully closed