source-command-catchup
Use this skill when the user asks to run the migrated source command catchup.
Command Template
Catchup: Understand the Project Deeply
Get up to speed with the entire project — history, direction, and details.
Phase 1: Git History Analysis
Recent Commits
git log --oneline -50
git log --oneline --since="1 week ago"
git log --oneline --since="1 month ago" --until="1 week ago"
Commit Patterns
- What areas are being actively worked on?
- What types of changes dominate? (feat, fix, refactor, docs)
- Who are the contributors and what do they focus on?
- Are there any recurring issues being fixed?
Recent Activity by Area
git log --oneline --all -- "src/components/*" | head -20
git log --oneline --all -- "src/api/*" | head -20
git log --oneline --all -- "src/lib/*" | head -20
Phase 2: Development Direction
Read Project Documentation
- PRODUCT.md — Vision, goals, target users, success metrics
- ARCHITECTURE.md — Tech decisions, patterns, system design
- AGENTS.md — Project-specific knowledge, commands, gotchas
- README.md — Setup, usage, contribution guidelines
- CHANGELOG.md — Release history, breaking changes
Identify Current Focus
- What features are in progress?
- What's the roadmap or next milestones?
- Are there open issues or PRs that indicate direction?
gh issue list --state open --limit 20
gh pr list --state open --limit 10
Business & Marketing Strategy
- What's the monetization model? Is it working?
- Who are the competitors? How does this differentiate?
- What's the go-to-market strategy?
- How are users being acquired? (SEO, social, paid, referral)
- What public-facing assets exist? (landing page, blog, socials)
Branch Analysis
git branch -a
git log main..HEAD --oneline # if on feature branch
Phase 3: Deep Implementation Research
Codebase Structure
tree -L 2 -d src/ # or relevant directories
Key Files to Understand
- Entry points (main, index, app)
- Configuration files (config, env, settings)
- Core business logic
- Database schema and migrations
- API routes and handlers
- Shared utilities and helpers
Dependency Analysis
- What are the major dependencies?
- Are there any custom abstractions worth understanding?
- What patterns are consistently used?
Test Coverage
- Where are tests located?
- What's tested, what's not?
- What do test failures tell us about the system?
Output
Executive Summary
Project: [name]
Stage: [MVP / Growth / Mature]
Focus: [current development focus]
Health: [assessment based on commits, issues, code quality]
Recent Activity (Last 2 Weeks)
| Date |
Area |
Changes |
Impact |
| ... |
... |
... |
H/M/L |
Development Direction
- Current sprint/focus: ...
- Next milestones: ...
- Technical debt: ...
- Opportunities: ...
Key Findings
- ...
- ...
- ...
Recommendations
- Immediate: ...
- Short-term: ...
- Consider: ...
Mindset
- Be thorough — read everything, assume nothing
- Connect the dots — understand WHY decisions were made
- Think forward — where is this project heading?
- Be critical — identify risks, gaps, opportunities
- Document discoveries — update AGENTS.md with important findings
1---2name: source-command-catchup3description: Deep dive into project history, direction, and implementation details4---56# source-command-catchup78Use this skill when the user asks to run the migrated source command `catchup`.910## Command Template1112# Catchup: Understand the Project Deeply1314Get up to speed with the entire project — history, direction, and details.1516## Phase 1: Git History Analysis1718### Recent Commits19```bash20git log --oneline -5021git log --oneline --since="1 week ago"22git log --oneline --since="1 month ago" --until="1 week ago"23```2425### Commit Patterns26- What areas are being actively worked on?27- What types of changes dominate? (feat, fix, refactor, docs)28- Who are the contributors and what do they focus on?29- Are there any recurring issues being fixed?3031### Recent Activity by Area32```bash33git log --oneline --all -- "src/components/*" | head -2034git log --oneline --all -- "src/api/*" | head -2035git log --oneline --all -- "src/lib/*" | head -2036```3738## Phase 2: Development Direction3940### Read Project Documentation411. **PRODUCT.md** — Vision, goals, target users, success metrics422. **ARCHITECTURE.md** — Tech decisions, patterns, system design433. **AGENTS.md** — Project-specific knowledge, commands, gotchas444. **README.md** — Setup, usage, contribution guidelines455. **CHANGELOG.md** — Release history, breaking changes4647### Identify Current Focus48- What features are in progress?49- What's the roadmap or next milestones?50- Are there open issues or PRs that indicate direction?5152```bash53gh issue list --state open --limit 2054gh pr list --state open --limit 1055```5657### Business & Marketing Strategy58- What's the monetization model? Is it working?59- Who are the competitors? How does this differentiate?60- What's the go-to-market strategy?61- How are users being acquired? (SEO, social, paid, referral)62- What public-facing assets exist? (landing page, blog, socials)6364### Branch Analysis65```bash66git branch -a67git log main..HEAD --oneline # if on feature branch68```6970## Phase 3: Deep Implementation Research7172### Codebase Structure73```bash74tree -L 2 -d src/ # or relevant directories75```7677### Key Files to Understand78- Entry points (main, index, app)79- Configuration files (config, env, settings)80- Core business logic81- Database schema and migrations82- API routes and handlers83- Shared utilities and helpers8485### Dependency Analysis86- What are the major dependencies?87- Are there any custom abstractions worth understanding?88- What patterns are consistently used?8990### Test Coverage91- Where are tests located?92- What's tested, what's not?93- What do test failures tell us about the system?9495## Output9697### Executive Summary98```99Project: [name]100Stage: [MVP / Growth / Mature]101Focus: [current development focus]102Health: [assessment based on commits, issues, code quality]103```104105### Recent Activity (Last 2 Weeks)106| Date | Area | Changes | Impact |107|------|------|---------|--------|108| ... | ... | ... | H/M/L |109110### Development Direction111- **Current sprint/focus:** ...112- **Next milestones:** ...113- **Technical debt:** ...114- **Opportunities:** ...115116### Key Findings1171. ...1182. ...1193. ...120121### Recommendations122- **Immediate:** ...123- **Short-term:** ...124- **Consider:** ...125126## Mindset127128* Be thorough — read everything, assume nothing129* Connect the dots — understand WHY decisions were made130* Think forward — where is this project heading?131* Be critical — identify risks, gaps, opportunities132* Document discoveries — update AGENTS.md with important findings
SylphxAI