grace-ask

Answer GRACE project questions with cited evidence from knowledge graph and source blocks.

233|51|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/osovv/grace-marketplace --skill grace-ask
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grace-ask
Source: https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-ask
Command: npx skills add https://github.com/osovv/grace-marketplace --skill grace-ask

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide concise, evidence-backed answers to questions about a GRACE codebase by loading and reasoning over the project's documentation, knowledge graph, module contracts, and source artifacts so users avoid speculation and get verifiable conclusions.

Core Features & Use Cases

  • Full project context loading: Reads AGENTS.md, knowledge graph XML, requirements, technology, development plans, module contracts, and relevant source blocks to build a grounded view.
  • Knowledge graph navigation: Locates related modules, follows CrossLinks, and identifies dependency surfaces to surface relevant components.
  • Code-level investigation and citations: Dives into MODULE_MAP locations and START_BLOCK/END_BLOCK sections to explain implementation details with explicit file/module citations.
  • Documentation gap detection: Flags missing contracts or unclear documentation and recommends appropriate $grace-* follow-up skills.
  • Use Case: A developer asks how authentication is implemented; the Skill locates related modules, reads contracts and code blocks, and returns a traced answer citing files and blocks.

Quick Start

Ask the agent a specific question about the repository and request explicit file and module citations in the answer.

Frequently Asked Questions about grace-ask

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

FAQPage Schema
How do I get grounded answers about my codebase architecture without speculation?

To get grounded answers about your codebase architecture, load project context like AGENTS.md, knowledge graph XML, module contracts, and source artifacts to generate verifiable responses with explicit file citations.

How do I trace implementation details in a module using a knowledge graph?

Trace implementation details by navigating the knowledge graph to locate related modules, follow CrossLinks, and read START_BLOCK/END_BLOCK sections in the source code to explain behavior with direct file and module citations.

Can I detect documentation gaps in my project's module contracts?

Yes, you can detect documentation gaps by loading module contracts and project artifacts to flag missing documentation, which then recommends appropriate follow-up skills to resolve the identified gaps.

What's the best way to answer reviewer questions about module behavior and dependencies?

Answer reviewer questions about module behavior by loading full project context including requirements, technology plans, and module contracts to locate evidence and produce verifiable conclusions with file citations.

Does this approach work for investigating how a specific feature like authentication is implemented?

Yes, investigating how a feature like authentication is implemented works by locating related modules, reading contracts and source code blocks, and returning a traced answer that cites the specific files and blocks involved.

When should I avoid using a knowledge graph for codebase questions?

Avoid using a knowledge graph for codebase questions when the project lacks structured documentation, knowledge graph XML, or defined module contracts, as the tool relies on these artifacts to provide grounded, cited responses.