ask

Answer codebase architecture and change impact questions with file:line references.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/yandy-r/claude-plugins --skill ask-yandy-r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask
Source: https://github.com/yandy-r/claude-plugins/tree/main/.cursor-plugin/skills/ask
Command: npx skills add https://github.com/yandy-r/claude-plugins --skill ask-yandy-r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide read-only guidance about the codebase, answering questions about architecture, implementation, and the impact of changes without modifying code.

Core Features & Use Cases

  • Read-only expert guidance about how a codebase works, where features are implemented, and how changes would affect other parts.
  • Returns precise file:line references and contextual architecture understanding to support decision making.
  • Supports guidance, impact analysis, and side-by-side comparison to help evaluate trade-offs.

Quick Start

Ask a codebase question using the /ask command to receive read-only, file:line-backed guidance.

Frequently Asked Questions about ask

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

FAQPage Schema
How do I get read-only codebase guidance without modifying files?

Read-only codebase guidance answers questions about architecture and implementation without modifying files. Use the /ask command to trigger the codebase-advisor agent, which returns precise file:line references.

How does impact analysis work when evaluating codebase changes?

Impact analysis evaluates how changes would affect other codebase components. The /ask command triggers a read-only agent that maps implementation dependencies and returns file:line references to support decision making.

Can I use /ask to find where a feature is implemented in a large codebase?

Yes, /ask supports codebases of varying sizes. It returns precise file:line references and contextual architecture understanding to pinpoint where features are implemented.

What is the best way to perform a code review without writing changes?

Read-only code review via /ask provides side-by-side comparison and architecture understanding to evaluate trade-offs. It avoids write operations and outputs file:line-backed guidance.

Are there limitations to using a read-only agent for codebase analysis?

The read-only agent avoids write operations, meaning it cannot modify, refactor, or fix code directly. It provides guidance, impact analysis, and file:line references to support manual changes.