Menu
Orient in an unfamiliar codebase by inspecting repository instructions, structure, documentation, manifests, key files, Git state, and recent work. Use when starting work, switching repositories, or needing a concise architecture overview.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Manage Azure DevOps via CLI including repos, pull requests, pipelines, builds, work items, and boards. Use when working with Azure DevOps, az devops commands, CI/CD pipelines, PRs, or Azure Boards work items.
Closed-loop planning discipline for non-trivial changes. Use when creating implementation plans, reviewing plan completeness, or preparing PRs that require structured planning evidence.
Fetch up-to-date library documentation. Use when user asks about libraries, frameworks, or needs current API references/code examples.
Design and create portable Agent Skills with effective triggers, concise instructions, and reusable scripts, references, or assets. Use when adding a new skill or substantially restructuring an existing skill.
Dispatch parallel subagents for independent tasks without shared state. Use when facing 2+ independent failures, debugging unrelated subsystems, or researching separate topics concurrently.
Manage GitHub via CLI including pull requests, issues, workflows, actions, releases, and repositories. Use when working with GitHub, gh commands, GitHub Actions CI/CD, PRs, issues, releases, or repository management.
| name | primer |
| description | Orient in an unfamiliar codebase by inspecting repository instructions, structure, documentation, manifests, key files, Git state, and recent work. Use when starting work, switching repositories, or needing a concise architecture overview. |
Build enough context to work safely without reading the repository exhaustively.
Read repository instructions in scope, then inspect:
git status --short --branch
git log --oneline -20
git remote -v
rg --files
Use a shallow tree when available and exclude generated dependency, cache, and build directories. If the request names a subdirectory, focus there while noting its relationship to the broader repository.
Read in this order, stopping when sufficient context is available:
AGENTS.md, CLAUDE.md, and scoped equivalents.README.md, contribution guides, and architecture documentation.package.json, pyproject.toml,
go.mod, Cargo.toml, and Makefile.Read instruction files fully. Scan manifests for commands and important dependencies rather than reading lockfiles or generated output.
Identify:
Prefer targeted reads. Note large files without loading them completely unless the active task requires it.
If the working tree is dirty, inspect git diff --stat and the relevant diffs
without reverting them. Use recent commits to identify the current development
focus. Surface uncertainty and repository risks instead of guessing.
## Primer Report: <project>
### Overview
- Type, purpose, languages, and frameworks
### Architecture
- Major directories, boundaries, entry points, and data flows
### Development
- Runtime, dependencies, build, test, lint, and CI commands
- Repository rules that affect the requested work
### Key Files
| File | Purpose |
|---|---|
### Current State
- Branch and working tree
- Recent development focus
- Risks, unknowns, and likely next investigation
Keep the report concise and evidence-based. Do not infer unsupported commands or architecture.