explore

Gathers read-only repository evidence via narrow, prompt-driven lookups with cited file outputs.

3|Updated May 24, 2026
One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill explore-shayne-snap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/explore
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill explore-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly answer concrete questions about a repository without risking accidental edits or unintended side effects.

Core Features & Use Cases

  • Read-only repository fact gathering: collect evidence about files, paths, symbols, and relevant commands for decision-making.
  • Narrow, prompt-driven lookup: supports repo-local queries such as key files (e.g., package.json or README) and targeted searches.
  • Evidence-first responses: instructs responses to cite specific files and exact command output used as proof for conclusions.

Quick Start

Use omagy explore with a narrow prompt to retrieve specific repository evidence as JSON for later planning.

Frequently Asked Questions about explore

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

FAQPage Schema
How do I gather read-only repository facts without risking accidental edits?

Read-only repository exploration allows you to safely gather codebase facts without risking accidental edits or unintended side effects. It enforces safety by preventing state changes and executing bounded, non-arbitrary commands.

What is the best way to extract evidence from a codebase for deep investigation?

Evidence-first codebase searches extract specific files, paths, and symbols to support deep investigation. Responses cite exact command outputs and files as proof for conclusions, ensuring reliable decision-making.

How do I find prior plan records and key files in a repository for project planning?

To unblock planning, perform narrow, prompt-driven lookups in your repository to find prior plan records and key files like package.json or README. This retrieves targeted codebase evidence as JSON for later use.

Can I execute shell commands during repository exploration without modifying files?

Yes, you can extract the results of safe shell routes during repository exploration without modifying files. The system enforces read-only access, preventing edits or state changes while using bounded command execution.

What are the limitations of using a read-only approach for repository exploration?

The main limitation of read-only repository exploration is that it prevents edits and state changes entirely. It is restricted to bounded, non-arbitrary command execution, meaning it cannot perform write operations or broad system modifications.