hoavdc/CodexKit / skills/codexkit-repo-onboarding
codexkit-repo-onboarding
VerifiedRapidly map a new codebase, identify the runtime model, risk zones, and first high-value next steps.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.3 KB |
| agents/openai.yaml | config | 194 B |
| examples/common-mistakes.md | markdown | 778 B |
| examples/good-output.md | markdown | 909 B |
| verification/checklist.md | markdown | 1.3 KB |
examples/good-output.md
View on GitHub# Good Output Example — Repo Onboarding
> This example demonstrates what well-executed repo onboarding output looks like.
## Scenario
Onboarding guide for a Node.js monorepo with 3 services
## Why It Works
1. Purpose: 'Handles user auth (auth-service), product catalog (catalog-api), and order processing (order-worker)'
2. Setup: 'Step 1: Clone. Step 2: nvm use (reads .nvmrc). Step 3: pnpm install. Step 4: docker compose up -d (Postgres + Redis).'
3. First task: 'Look at packages/catalog-api/src/routes/product.ts — add a new GET endpoint for /products/:id/reviews'
4. Gotcha: 'order-worker uses Bull queues — if Redis isn't running, it fails silently. Check docker ps first.'
## Key Patterns to Replicate
- Setup is copy-paste-able — each step is a single command
- Architecture is visual: folder tree + data flow diagram
- First task is concrete, achievable, and teaches the key patterns
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |