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 doctorPrint the full checklist from the CLI:
npx pastoralist onboardInstall Pastoralist and create the initial config:
npm install pastoralist --save-devnpx pastoralist initUpdate the appendix once the config is in place:
npx pastoralistKeep it current after dependency installs:
npx pastoralist --setup-hookInstall only the bundled Pastoralist skill:
npx pastoralist --init agent-skillPreview local dev setup before writing files:
pnpm run setup:local-dev -- --dry-runSet up agent config, bundled skills, and local hooks:
pnpm run setup:local-dev -- --skills all --hooks git,postinstallThe local dev setup script auto-detects Codex or Claude when possible. You can pin the target explicitly:
pnpm run setup:local-dev -- --agent codexpnpm run setup:local-dev -- --agent claudeUse 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 `pnpm run 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.pnpm run setup:local-dev -- --dry-run.npx pastoralist --dry-run.Create .github/workflows/pastoralist.yml:
name: Override Checkon: [pull_request] jobs: pastoralist: runs-on: ubuntu-latest steps: - uses: actions/checkout@v7 - uses: yowainwright/pastoralist@v1 with: mode: check check-security: falseUse these commands before merging setup changes:
npx pastoralist --dry-runnpx pastoralist --summarynpx pastoralist --checkSecuritynpx pastoralist doctornpx pastoralist onboardnpm install pastoralist --save-dev
npx pastoralist initnpx pastoralistnpx pastoralist --setup-hooknpx pastoralist --init agent-skillpnpm run setup:local-dev -- --dry-runpnpm run setup:local-dev -- --skills all --hooks git,postinstallpnpm run setup:local-dev -- --agent codex
pnpm run setup:local-dev -- --agent claudeSet up Pastoralist in this repository.
Start with `npx pastoralist doctor` and inspect the current package manager setup.
Run `pnpm run 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: falsenpx pastoralist --dry-run
npx pastoralist --summary
npx pastoralist --checkSecurity