repo-check

Small repo maintenance CLI for generic repository housekeeping.

Commands

repo-check check [path]
repo-check check --all [path]
repo-check sync [path]
repo-check sync --all [path]
repo-check clone

repo-check check checks the current package directory by default.

repo-check check --all recursively finds package directories under the target directory and checks each one.

repo-check sync runs git pull for the enclosing git repo of the target path.

repo-check sync --all recursively finds git repositories under the target directory and runs git pull in each one.

repo-check clone is reserved but not implemented yet.

What It Checks

For each package directory it checks, repo-check currently verifies:

• the directory contains a package.json
• the directory is inside a git repository
• the enclosing git repo path follows a two-tier structure: <org>/<repo>
• the package identity is @<org>/<package-dir-name>
• package.json exists and is valid JSON
• package.json.name is exactly @<org>/<package-dir-name>
• package.json.version exists and is non-empty
• package.json.license exists and is non-empty
• package.json.copyright exists and is non-empty
• a package-local LICENSE file exists
• the package LICENSE file contains the exact copyright string from package.json.copyright
• a package-local CHANGES file exists
• the first Version ... line in CHANGES matches Version <package.json.version> (<YYYY-MM-DD>)
• the year in the top CHANGES version line appears in package.json.copyright
• the enclosing git repo origin remote matches <org>/<repo>
• the enclosing git repo branch has an upstream configured
• the enclosing git repo can fetch upstream updates
• the enclosing git repo branch is exactly in sync with its upstream
• the enclosing git repo does not contain agent files or agent directories such as AGENTS.md, CLAUDE.md, codex.md, .claude, or .codex
• the enclosing git repo has a repo-root lockfile such as pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb, or bun.lock
• any GitHub workflow under .github/workflows uses actions/setup-node@v6
• any GitHub workflow under .github/workflows sets node-version: 24
• GitHub workflows do not reference node20 or node22
• the git working tree is clean for files under that package directory
• if there are modifications beyond CHANGES in that package directory, then that package's CHANGES must also be modified

Exit status:

• 0 if every checked repository passes
• 1 if any check fails or if the CLI usage is invalid

Install

npm install -g @technomoron/repo-check