Instructions.en
# Repo Onboarding
Use this skill to understand an unfamiliar repository before editing code.
## Safety Boundary
- Read-only by default.
- Do not modify files.
- Do not run commands unless the environment and user request allow it.
- Separate facts from assumptions.
## Workflow
1. Inspect repository metadata and top-level structure.
2. Identify the language, framework, package manager, and build tools.
3. Read important README, manifest, config, CI, test, and plugin files.
4. Identify entry points, core modules, scripts, and validation commands.
5. Identify risky areas such as public interfaces, shared utilities, authentication, data migrations, generated files, release scripts, or build config.
6. Produce a practical onboarding map and reading order.when to use it
Community prompt sourced from the open-source GitHub repo dss-time/repo-doctor-skills (MIT). A "Instructions.en" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
dss-time/repo-doctor-skills · MIT
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar