From graqle
Fix a bug through GraQle's governed workflow — investigate with the knowledge graph, check blast radius, plan, generate a reviewed diff, and teach the outcome back to the graph. Use when fixing bugs in a repository that has a GraQle knowledge graph (graqle.json / graqle.yaml present) and the GraQle MCP server connected.
How this skill is triggered — by the user, by Claude, or both
Slash command
/graqle:governed-bug-fixThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fix bugs through GraQle's governance chain instead of ad-hoc editing. Every phase
Fix bugs through GraQle's governance chain instead of ad-hoc editing. Every phase uses a GraQle MCP tool; run the phases in order and do not skip any.
graq_lifecycle(event="session_start") once per session. Loads graph
status and past lessons relevant to your task.graq_reason(question=<the exact symptom>) to reason over the
graph, then graq_inspect on the affected file or module.graq_safety_check(component=<file>). If risk comes back
CRITICAL, stop and confirm with the user before touching anything.graq_plan(goal=..., scope=...) to get a governance-gated execution
plan before any file changes.graq_generate(..., dry_run=true); show the user the diff and get
approval before applying.graq_edit(dry_run=false); prefer strategy="literal" for exact,
deterministic replacements.graq_review on the applied change. Fix findings and re-review until
it approves with no blockers.graq_learn(mode="outcome", action=..., outcome=..., lesson=...).
Never skip this: the graph must learn from every fix.Guidelines:
graq_context over reading many files manually.npx claudepluginhub quantamixsol/graqle --plugin graqleОтладка и исправление проблемы через GRACE-семантическую навигацию с паттерном Prove-It. Использовать при встрече с багами, ошибками или неожиданным поведением — пройти по графу, плану верификации и семантическим блокам, написать ПАДАЮЩИЙ тест, который доказывает баг, применить точечное исправление, убедиться в прохождении теста и защититься от регрессии.
Autonomous bugfix workflow from invocation to merged PR with no questions gate, spec generation, or planning phase. Use for bugs, patches, and small well-defined changes scoped to 1-3 files.