Thanks for improving dev-toolbox.
- Run baseline checks:
./scripts/doctor
./scripts/doctor-ci . --strict- Run functional checks:
./scripts/smoke .- If you change profiles/templates/scaffolding, validate generated repos:
tmpdir=$(mktemp -d)
./scripts/scaffold ci-node-cli node-cli "$tmpdir" --no-install --force
./scripts/scaffold ci-next next-app "$tmpdir" --no-install --force
./scripts/scaffold ci-action github-action "$tmpdir" --no-install --force
./scripts/doctor-ci "$tmpdir/ci-node-cli" --strict
./scripts/doctor-ci "$tmpdir/ci-next" --strict
./scripts/doctor-ci "$tmpdir/ci-action" --strict- Keep PRs scoped to one clear outcome.
- Include rationale and tradeoffs for non-trivial changes.
- Update docs and changelog for user-facing behavior changes.
- Use semantic PR titles (
feat:,fix:,docs:,chore:etc.).
Conventional commits are preferred:
feat:new capabilityfix:bug fixdocs:documentation updateschore:maintenance work
Use ./scripts/changelog --apply to generate [Unreleased] notes before cutting releases.