grepo-subagent

Delegate repo-grounded research tasks to a subagent analyzing grepo snapshots.

1|Updated Aug 24, 2025
One-click install
npx skills add https://github.com/tomrford/config --skill grepo-subagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grepo-subagent
Source: https://github.com/tomrford/config/tree/main/.agents/skills/grepo-subagent
Command: npx skills add https://github.com/tomrford/config --skill grepo-subagent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegate repo-grounded research tasks to a dedicated subagent that analyzes grepo-managed snapshots.

Core Features & Use Cases

  • Spawn a focused subagent for targeted codebase analysis against grepo snapshots.
  • Return grounded findings with exact file paths and concise evidence to inform decisions.
  • Use cases include inspecting a project in grepo/ or answering research questions against pinned aliases.

Quick Start

Spawn a read-only subagent to inspect the grepo alias and report grounded findings with exact file paths.

Frequently Asked Questions about grepo-subagent

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

FAQPage Schema
How do I delegate codebase analysis to a subagent for repo research?

To delegate codebase analysis, you spawn a read-only subagent to inspect grepo-managed snapshots and return concise, grounded findings with exact file paths.

What is a grepo snapshot and when do I need it for code analysis?

A grepo snapshot is a pinned repository alias stored under grepo/. You need it when you want targeted codebase research conducted against a specific, stable version of your project.

Do I need existing aliases and a grepo setup to run repo research?

Yes, you need the grepo setup with a grepo/.lock file and existing aliases under grepo/ before spawning the subagent to analyze the snapshots.

Can I get grounded evidence with exact file paths from a codebase analysis?

Yes, the subagent analyzes grepo-managed snapshots and returns grounded findings with exact file paths and concise evidence to inform your decisions.

What's the best way to research a project pinned in grepo?

The best way is to spawn a focused, read-only subagent that inspects the grepo alias and reports targeted grounded findings with exact file paths.

Are there limitations when using a subagent for repo research?

Yes, the subagent is read-only and limited to analyzing existing grepo-managed snapshots, meaning it cannot modify files or research repositories without pre-configured aliases.