ze-explore

Search repository topics and propose non-editing change paths.

50|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ze-software/ze --skill ze-explore
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ze-explore
Source: https://github.com/ze-software/ze/tree/main/.codex/skills/ze-explore
Command: npx skills add https://github.com/ze-software/ze --skill ze-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables rapid topic research within the Ze repository by locating and summarizing relevant files across internal/, pkg/, cmd/, tests, plan/, docs/, and rules, and by proposing a non-editing change path to guide development decisions.

Core Features & Use Cases

  • Cross-repo topic discovery by scanning internal/, pkg/, cmd/, tests, plan/, docs/, and rules.
  • Read all relevant matches to understand current behavior and constraints.
  • Generate a concise summary of findings and propose the most plausible extension path aligned with existing patterns without modifying code.

Quick Start

Ask Ze to explore a topic and return a concise summary plus a proposed non-editing change path.

Frequently Asked Questions about ze-explore

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

FAQPage Schema
How do I research a topic across a repository before planning code changes?▼

Researching a topic across a repository involves scanning directories like internal/, pkg/, and docs/ to read current behavior and generate a summary with a non-editing change path for pre-implementation analysis.

What is the best way to summarize repository files for a design review?▼

To summarize repository files for a design review, locate relevant matches across cmd/, tests/, and rules, then synthesize current constraints to output a plausible extension path aligned with existing patterns.

Can I analyze internal code patterns and tests without modifying the actual source files?▼

Yes, analyzing internal code patterns and tests without modifying source files is possible by reading all relevant matches to understand constraints and outputting a concrete, non-editing change path that aligns with existing patterns.

Does pre-change repository analysis work for documentation updates and topic research?▼

Yes, pre-change repository analysis works for documentation updates and topic research by applying cross-repo discovery to scan plan/, docs/, and rules directories, summarizing findings to guide development decisions.

When do I need a non-editing change path for repository topic research?▼

You need a non-editing change path for repository topic research when you want to understand current behavior and propose a plausible extension path for pre-change decisions without directly modifying code.