developer-onboarding-doc
Write a developer onboarding document for a service, codebase, or team. Use when asked to write a developer guide, service README, onboarding doc for a new engineer, codebase orientation, or getting-started guide for a technical team. Produces a structured doc covering service overview, architecture, local setup, key patterns, testing, deployment, and who to ask for what.
npx skills add mohitagw15856/pm-claude-skills --skill developer-onboarding-doc --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Developer Onboarding Document Skill Produce a complete developer onboarding document for a service or team — covering everything a new engineer needs to be productive within their first week. A good onboarding doc is not a wiki dump. It answers the questions a new engineer actually has on day one, in the order they'll have them. ## Required Inputs Ask for these if not already provided: - **Service name** and what it does - **Team** responsible for it - **Tech stack** — language(s), framework(s), database(s), message queues, etc. - **Key external dependencies** — upstream services, third-party APIs - **Deployment target** — Kubernetes, ECS, Lambda, bare metal, etc. - **Local dev setup** — how to run locally (Docker Compose, local DB, etc.) - **Testing approach** — unit, integration, E2E; test commands - **Deployment process** — summary of how code gets to production - **On-call setup** — who's on-call, how alerts work - **Contacts** — tech lead, platform team, related service owners ## Output Format --- # Developer Onboarding: [Service Name] **Team:** [Team name] | **Tech lead:** [Name] **Last updated:** [Date] | **Updated by:** [Name] > If something in this doc is wrong or out of
- Required Inputs
- Output Format
- What This Service Does
- Codebase Orientation
- Key directories
- Things that might surprise you
- Local Development Setup
- Prerequisites
- Step-by-step setup
- Environment Variables
- Useful local commands
- Testing
- Running tests
- Writing tests
git clone [repo URL] cd [repo-name] cp .env.example .env Edit .env — see "Environment Variables" section below curl http://localhost:[PORT]/health All tests Unit tests only Integration tests (requires local deps running) A specific test file or test case Create a new migration
What does the developer-onboarding-doc skill do?
Write a developer onboarding document for a service, codebase, or team. Use when asked to write a developer guide, service README, onboarding doc for a new engineer, codebase orientation, or getting-started guide for a technical team. Produces a structured doc covering service overview, architecture, local setup, key patterns, testing, deployment, and who to ask for what.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill developer-onboarding-doc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.