Locate semantic blocks and apply contract-aligned fixes in GRACE-instrumented codebases.
npx skills add https://github.com/osovv/grace-marketplace --skill grace-fix
Please help me install this Agent Skill. Skill: grace-fix Source: https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-fix Command: npx skills add https://github.com/osovv/grace-marketplace --skill grace-fix
GRACE-Fix addresses the challenge of debugging complex codebases instrumented with semantic markers and contracts where locating the responsible module and the exact implementation block is time-consuming and error-prone. It gives a structured procedure to navigate the project's knowledge graph, find the semantic block referenced by logs or module maps, and resolve mismatches between a block's CONTRACT and its implementation without breaking semantic boundaries.
Ask the agent to debug the reported error by locating the module in docs/knowledge-graph.xml, tracing the START_BLOCK marker to the semantic block, comparing the block code to its CONTRACT, and proposing a minimal in-block fix.
High-intent search queries and answers about installing and using this skill.
To debug runtime errors using a semantic knowledge graph, navigate the project's docs/knowledge-graph.xml to identify the target module, trace START_BLOCK markers to the exact code region, and compare the implementation against its CONTRACT to apply a minimal in-block fix.
To fix code that violates its module CONTRACT, locate the responsible semantic block via START_BLOCK markers, compare the intended behavior from the CONTRACT against the current implementation, and apply targeted contract-aligned modifications within that block's boundaries.
Contract-driven fixes resolve mismatches between a code block's intended behavior and its actual implementation by comparing against module CONTRACTs, ensuring that modifications stay within semantic boundaries and do not break cross-link dependencies defined in the knowledge graph.
Yes, tracing semantic blocks requires a codebase instrumented with GRACE semantic markers, a docs/knowledge-graph.xml file, module CONTRACTs, and code search capabilities to locate START_BLOCK markers for safe in-block modifications.
After applying a contract-aligned code fix, you should update the CHANGE_SUMMARY and metadata, then run verification steps including type checking, linting, and strengthening tests or logs to ensure the modification maintains system integrity.
osovvGenerate GRACE-marked module code with contract fidelity and graph synchronization.
BingChanCNRun a pre-commit checklist covering linting, type checking, tests, and API changes.
loriensleafsTraverse the Brain knowledge graph to surface notes, observations, and relations.
FaysilAlshareefDiagnose root causes of . .NET build and runtime failures with structured debugging workflows.
