public-repo-explorer
Public Repo Explorer
Overview
Use this skill to safely and efficiently explore open-source / public repositories.
Workflow
-
Create a Temporary Workspace:
- Create a temporary directory on the user's machine to hold the repository safely without cluttering their main workspace.
- Command:
mkdir -p /tmp/agent-repo-scan-<repo_name> && cd /tmp/agent-repo-scan-<repo_name>
-
Perform a Shallow Clone:
- Do NOT use the GitHub API or
ghCLI to avoid authentication blocks or rate limits. - Use standard git over HTTPS with the
--depth 1flag to download only the latest commit. - Why? Because as an AI agent, you rarely need the full git history to answer questions about the current codebase, and full clones waste massive amounts of time, bandwidth, and context window space.
- Command:
git clone --depth 1 <REPOSITORY_URL> .
- Do NOT use the GitHub API or
-
Analyze the Architecture:
More from eho/agent-skills
user-story-implementer
Implement a single user story or task from a GitHub Issue backlog. Executes a single iteration by fetching the next open issue, assigning it, implementing the code, creating a branch and PR, and moving on. You MUST use this skill when asked to "implement a user story", "run one iteration", "do the next task", or "complete a task from the backlog".
39user-story-reviewer
Review an implemented user story or task (via GitHub Pull Request) for completeness, test coverage, and code quality. Use this when asked to QA, review a PR, verify implementation, or as a follow-up to the user-story-implementer skill.
32prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
26prd-to-github-milestone
Parses a Product Requirements Document (PRD) to extract User Stories and creates corresponding GitHub Issues. It can optionally link them to a GitHub Milestone. This skill acts as a setup phase for GitHub-native issue tracking. Make sure to use this skill whenever the user asks to "send the PRD to GitHub", "create issues from the PRD", "setup the milestone", or mentions turning requirements into actionable GitHub issues.
18design-doc-reviewer
Review a design document for completeness, clarity, and quality — including user story readiness for agent implementation. Produces structured feedback with specific gaps, strengths, and a prioritized improvement checklist. Use when asked to review a design doc, critique a design, check a spec, review the PRD, or audit the requirements.
13post-implementation-reviewer
Performs a comprehensive post-implementation review of an entire design document. Verifies all user stories are complete, implementation aligns with the original design, code quality is high, and all documentation (READMEs, usage guides, API docs) is consistent and updated. Use this when asked to "do a final review of the design doc", "verify completion", "check if the feature is ready for release", or "audit the implementation".
9