Quickly understand a codebase by scanning its structure, conventions, dependencies, and patterns. The output is a concise summary delivered in chat — no files created.
Announce at start: "Using gather-context skill to scan the project."
When to Use
- Starting work on an unfamiliar codebase
- Coming back to a project after a break
- Before brainstorming or planning, when context is needed fast
- When the user says "what's going on in this project?" or "catch me up"
Checklist
Create a task for each item and complete them in order. Run scans in parallel where possible.
1. Project identity
- Find the package manifest (
package.json, go.mod, Cargo.toml, pyproject.toml, .csproj, Directory.Build.props, etc.)
- Identify: name, language, framework, runtime version
- Read
README.md or docs/SPEC.md for the project description
2. Structure
- List top-level directories and files
- Drill into each major directory to understand purpose
- Note entry points (
main.go, src/index.ts, cmd/, apps/, packages/)
- Identify monorepo layout if present (workspaces, packages, apps)
3. Commands
- Check
package.json scripts, Makefile, justfile, Taskfile.yml, .csproj targets, or equivalent
- Identify: dev server, build, test, lint, format, typecheck
- Note the pre-commit gate (which commands must pass)
4. Dependencies
- Scan runtime and dev dependencies
- Identify the key libraries the project relies on
- Note version constraints or pinned versions
5. Conventions and patterns
- Read
AGENTS.md or equivalent config if it exists
- Check linter/formatter configs
- Identify coding patterns: state management, auth flow, data layer, error handling
- Note any non-obvious conventions (naming, file organization, import style)
6. Recent activity
- Check recent git log (last 5-10 commits) to understand what's been happening
- Check for uncommitted changes
Output Format
Present a concise summary in chat. Keep it scannable.
## Context: <project name>
**What it is:** <1 sentence>
**Stack:** <language, framework, key deps>
**Structure:** <brief layout description>
**Commands:**
- `cmd` — what it does
**Key patterns:**
- <pattern> — <where it lives>
**Recent activity:**
- <last few commits or active work>
If the user asked about something specific, focus the summary on that area. Skip sections that aren't relevant to what they're about to do.
Key Principles
- Fast, not exhaustive. This is a quick scan, not a deep audit. Target 2-3 minutes.
- Focused on what matters next. If the user is about to build a feature, emphasize the files and patterns they'll touch. If they're just exploring, give the broad picture.
- No files created. The output is a chat summary. If the user wants persistent context, that's what the sync-agents skill is for.
- Skippable. If context is already clear from the conversation, say so and skip the scan.
1---2name: gather-context3description: Use when the user wants to quickly understand a codebase or project before doing work. Scans structure, conventions, dependencies, and patterns. Produces a concise summary, not files.4---56Quickly understand a codebase by scanning its structure, conventions, dependencies, and patterns. The output is a concise summary delivered in chat — no files created.78**Announce at start:** "Using gather-context skill to scan the project."910## When to Use1112- Starting work on an unfamiliar codebase13- Coming back to a project after a break14- Before brainstorming or planning, when context is needed fast15- When the user says "what's going on in this project?" or "catch me up"1617## Checklist1819Create a task for each item and complete them in order. Run scans in parallel where possible.2021### 1. Project identity2223- Find the package manifest (`package.json`, `go.mod`, `Cargo.toml`, `pyproject.toml`, `.csproj`, `Directory.Build.props`, etc.)24- Identify: name, language, framework, runtime version25- Read `README.md` or `docs/SPEC.md` for the project description2627### 2. Structure2829- List top-level directories and files30- Drill into each major directory to understand purpose31- Note entry points (`main.go`, `src/index.ts`, `cmd/`, `apps/`, `packages/`)32- Identify monorepo layout if present (workspaces, packages, apps)3334### 3. Commands3536- Check `package.json` scripts, `Makefile`, `justfile`, `Taskfile.yml`, `.csproj` targets, or equivalent37- Identify: dev server, build, test, lint, format, typecheck38- Note the pre-commit gate (which commands must pass)3940### 4. Dependencies4142- Scan runtime and dev dependencies43- Identify the key libraries the project relies on44- Note version constraints or pinned versions4546### 5. Conventions and patterns4748- Read `AGENTS.md` or equivalent config if it exists49- Check linter/formatter configs50- Identify coding patterns: state management, auth flow, data layer, error handling51- Note any non-obvious conventions (naming, file organization, import style)5253### 6. Recent activity5455- Check recent git log (last 5-10 commits) to understand what's been happening56- Check for uncommitted changes5758## Output Format5960Present a concise summary in chat. Keep it scannable.6162```63## Context: <project name>6465**What it is:** <1 sentence>66**Stack:** <language, framework, key deps>67**Structure:** <brief layout description>6869**Commands:**70- `cmd` — what it does7172**Key patterns:**73- <pattern> — <where it lives>7475**Recent activity:**76- <last few commits or active work>77```7879If the user asked about something specific, focus the summary on that area. Skip sections that aren't relevant to what they're about to do.8081## Key Principles8283- **Fast, not exhaustive.** This is a quick scan, not a deep audit. Target 2-3 minutes.84- **Focused on what matters next.** If the user is about to build a feature, emphasize the files and patterns they'll touch. If they're just exploring, give the broad picture.85- **No files created.** The output is a chat summary. If the user wants persistent context, that's what the sync-agents skill is for.86- **Skippable.** If context is already clear from the conversation, say so and skip the scan.
justincordova