Onboarding
First-run checklist for local use, agent setup, and CI
First-run checklist for local use, agent setup, and CI
Use onboarding when you are adding Pastoralist to a repo for the first time or when you want a repeatable setup path for contributors and agents.
Check the current project without writing files:
npx pastoralist doctor
Print the full checklist from the CLI:
npx pastoralist onboard
Install Pastoralist and create the initial config:
npm install pastoralist --save-dev
npx pastoralist init
Update the appendix once the config is in place:
npx pastoralist
Keep it current after dependency installs:
npx pastoralist --setup-hook
Install only the bundled Pastoralist skill:
npx pastoralist --init agent-skill
Preview local dev setup before writing files:
npx -p pastoralist pastoralist-setup-local-dev --dry-run
Set up agent config, bundled skills, and local hooks:
npx -p pastoralist pastoralist-setup-local-dev --skills all --hooks git,postinstall
The local dev setup script auto-detects Codex or Claude when possible. You can pin the target explicitly:
npx -p pastoralist pastoralist-setup-local-dev --agent codex
npx -p pastoralist pastoralist-setup-local-dev --agent claude
Use this prompt when you want an agent to do the setup:
Set up Pastoralist in this repository.
Start with `npx pastoralist doctor` and inspect the current package manager setup.
Run `npx -p pastoralist pastoralist-setup-local-dev --dry-run` before writing files.
Configure the Pastoralist skill, local agent config, GitHub Action, and postinstall hook only when appropriate.
Keep changes scoped to setup files, docs, and tests.
Use this prompt when you want an agent to review an existing setup:
Review this repository's Pastoralist setup.
Run `npx pastoralist --dry-run` and summarize stale overrides, security checks, and missing setup.
Do not remove overrides unless `npx pastoralist --remove-unused --dry-run` shows they are unused.
If setup is missing, propose the smallest script, skill, hook, or GitHub Action change.
Use this loop when an agent owns the setup:
npx pastoralist doctor.npx -p pastoralist pastoralist-setup-local-dev --dry-run.npx pastoralist --dry-run.Create .github/workflows/pastoralist.yml:
name: Override Check
on: [pull_request]
jobs:
pastoralist:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- uses: yowainwright/pastoralist@v1
with:
mode: check
check-security: false
Use these commands before merging setup changes:
npx pastoralist --dry-run
npx pastoralist --summary
npx pastoralist --checkSecurity
npm install pastoralist --save-dev
npx pastoralist init
npx pastoralist
npx pastoralist --setup-hook
npx pastoralist --init agent-skill
npx -p pastoralist pastoralist-setup-local-dev --dry-run
npx -p pastoralist pastoralist-setup-local-dev --skills all --hooks git,postinstall
npx -p pastoralist pastoralist-setup-local-dev --agent codex
npx -p pastoralist pastoralist-setup-local-dev --agent claude
Set up Pastoralist in this repository.
Start with `npx pastoralist doctor` and inspect the current package manager setup.
Run `npx -p pastoralist pastoralist-setup-local-dev --dry-run` before writing files.
Configure the Pastoralist skill, local agent config, GitHub Action, and postinstall hook only when appropriate.
Keep changes scoped to setup files, docs, and tests.
Review this repository's Pastoralist setup.
Run `npx pastoralist --dry-run` and summarize stale overrides, security checks, and missing setup.
Do not remove overrides unless `npx pastoralist --remove-unused --dry-run` shows they are unused.
If setup is missing, propose the smallest script, skill, hook, or GitHub Action change.
name: Override Check
on: [pull_request]
jobs:
pastoralist:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- uses: yowainwright/pastoralist@v1
with:
mode: check
check-security: false
npx pastoralist --dry-run
npx pastoralist --summary
npx pastoralist --checkSecurity