cp-skill-validate git:20261009.53b0dc6A

Immutable. This exact content never changes and is served at /api/v1/blob/1c7e8d096dfe5852.

---
name: cp-skill-validate
description: Run deterministic validation on KB artifacts, collections, collection landings, and the published redirect map, including schemas, links, required sections, and batch signals.
type: types/instruction.md
user-invocable: true
allowed-tools: Bash
context: fork
---

## EXECUTE NOW

Run the packaged validation command. For a draft at an intended set member
role, use the supplied paths as separate arguments:

```bash
commonplace-validate <draft> --artifact <directory> --role <role>
```

Quote each path as needed. The role must be a declared relative member
filename. This mode writes nothing, including no receipt or scratch log;
do not use `--output`. It checks the candidate's content in the working artifact,
not job acceptance. Acceptance may add labelled invocation residue. Report
that distinction with a pass. Use `--json` for findings with explicit repair
fields, or default/`--full` output for the shared rendered finding text.

For ordinary targets, follow the script below. For `all`, invoke each top-level collection separately because the CLI deliberately rejects a repository-wide literal scope. Run every check even after a failure, and report failure at the end:

```bash
if [ "$ARGUMENTS" = "all" ]; then
  status=0
  for contract in kb/*/COLLECTION.md; do
    commonplace-validate "$(basename "$(dirname "$contract")")" || status=1
  done
  commonplace-validate landings || status=1
  if [ -f properdocs.yml ]; then
    commonplace-validate redirects || status=1
  fi
  exit $status
else
  commonplace-validate "$ARGUMENTS"
fi
```

**Target: $ARGUMENTS**

Prefer the narrowest target that covers the user's request. For write/edit workflows, validate the new or edited file paths explicitly; do not validate the whole KB unless the user asked for a full maintenance check.

- Draft plus artifact directory and role: use the draft mode above
- Note path or name: validate that specific note
- Multiple note paths: validate those specific notes, one command per path if needed
- Directory path or collection name: validate `.md` files under that directory, only when the edited set is directory-scoped
- "all": validate each top-level collection in a separate command
- "landings": validate that every top-level collection has a non-colliding `README.md`
- "redirects": validate the live `properdocs.yml` redirect map against its published tree
- "notes": validate all `.md` files in `kb/notes/`
- "recent" or "today": validate notes modified today
- Empty: ask which note to validate

Report the script output directly. Do not interpret, supplement, or override its findings.

For judgment-based frontmatter checks, run [run-review-batches](../run-review-batches.md), resolved from this skill's real location, with the `frontmatter` bundle.