standpoint-review
Standpoint review — check a change from the side that RECEIVES it: copy the receiving repo (or a clean install of the package) into an isolated folder, apply the change there, run that repo''s OWN checks, have a reviewer judge the change against that repo''s OWN rules with none of the author''s explanation, then verify every finding against the source before acting on it. Use when asked whether a change breaks, or still works with, another repo, app, harness or package consumer that depends on it. Triggers: "입장 리뷰", "받는 쪽에서 돌려 봐", "하위 레포에서 돌려 봐", "그 레포 규칙으로 검증해 줘", "standpoint review", "run it from the target", "check it from the downstream repo", "make sure it won''t break the repo that depends on it", "will this change break downstream users".
chrono-meta · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add chrono-meta/forge-harness --skill standpoint-reviewAbout this skill
name: standpoint-review description: 'Standpoint review — check a change from the side that RECEIVES it: copy the receiving repo (or a clean install of the package) into an isolated folder, apply the change there, run that repo''s OWN checks, have a reviewer judge the change against that repo''s OWN rules with none of the author''s explanation, then verify every finding against the source before acting on it. Use when asked whether a change breaks, or still works with, another repo, app, harness or package consumer that depends on it. Triggers: "입장 리뷰", "받는 쪽에서 돌려 봐", "하위 레포에서 돌려 봐", "그 레포 규칙으로 검증해 줘", "standpoint review", "run it from the target", "check it from the downstream repo", "make sure it won''t break the repo that depends on it", "will this change break downstream users".' version: 0.1
standpoint-review — review a change from the side that receives it
Input: the change (a diff such as git diff <base>..HEAD > change.diff, a dependency bump, or a
package build) and the repo or package that receives it.
What it is, in one line: family diversity (another model reads the diff) raises resolution within one standpoint. Standpoint review changes which ground truth the change is checked against: the receiving side's own rules, tests and conventions. A defect that only exists relative to the receiver's conventions is invisible from the author's repo however many models read it.
Why this exists (operator decision 2026-11-01): in forge-harness (FH) the standpoint axis runs as
an engine — a rule (knowledge/shared/harness-core/field_verdict_crossfamily_gate.md §7) plus a
commit-hook field (standpoint:) — for sessions running inside the harness repo. Someone who only
installs the plugin gets neither. This skill is the same procedure as a doorway they can call.
The rule file stays the canon; read it whenever it is present. This skill does not replace it.
🚫 Not role-play. «Act as if you were repo X» is a prompt-level disguise, not a standpoint. The receiver has to actually run: its files, its checks, its rules loaded from its own tree.
Step 0 — Does this apply? (decide before doing anything)
Answer does this change alter how something else behaves — another repo, another harness, a plugin consumer, or what a package delivers to its installers? List every receiver, not the first one:
- A named receiver (a downstream repo, a sibling harness) → one target per repo.
- An installer of a package → one more target: a clean install of the packed artifact
(
npm pack→ install into an empty folder), not the source tree. - None → report
standpoint: not-applicable(<what you checked>)and stop. Most changes have no receiver. That is a valid result, not a failure.
Confidential receivers — decide here, before any copy is made. A receiver holding company source,
customer data, secrets or internal names (or whose owner says so) must not have its content read by
any remote model, of any family, nor by a web tool or a paste service. That includes the session
running this skill: Steps 1–4 read the receiver's files and check output. So for such a receiver, run
Steps 1–4 only in a runtime the receiver's owner already uses for that repo under its own rules. If no
such runtime is available, record DEGRADED_NOT_RUN(confidential — no approved local runtime) for that
target and do not copy it.
A change that alters both a downstream repo and the published package owes both. Run Steps 1–5
once per target and emit one standpoint: line per target. Recording only the first hides the
second.
Step 1 — Isolate the receiver (never work in the real one)
- Make a fresh folder outside every repository (for example under
/private/tmpor$TMPDIR). Check that no parent folder holds aCLAUDE.md,AGENTS.mdor.git. A session started inside a repo loads that repo's instructions, and they leak into the review. - Copy the receiver in with
git clone --no-hardlinks <receiver> <copy>, thengit -C <copy> remote remove origin, so that nothing run in the copy can push. Do not usegit worktree add. It writes a worktree entry and a branch into the real receiver's.git. For an installer target,npm packthe change and install the tarball into an empty folder. - Make a temporary
HOMEfor this run (mkdir <tmp>/home). Run every receiver check in Steps 2–4 withHOME=<tmp>/home. A receiver's own scripts may write to~/…or read real credentials. - Find the receiver's checks (Step 2 says where) and run them once before applying the change.
That is the baseline for Step 2. First install the receiver's dependencies inside the copy with
HOME=<tmp>/home: a clone has only committed files. Gitignored config or secrets the checks need will be missing; if you cannot restore one, write the check it blocks asUNMEASUREDin the Output. - Apply the change to the copy as an uncommitted patch (
git -C <copy> apply <diff>), or as a dependency bump or package install. Do not apply it as a branch with commits: commit messages carry the author's rationale into the copy'sgit log, where the reviewer can read it. - 🟥 Never apply the change to the receiver's real checkout, and never push or publish from the copy.
- The copy and the temporary
HOMEare precautions, not a sandbox: a receiver script that uses an absolute path can still reach the real checkout or real credentials. Recordgit -C <receiver> status --porcelain --ignoredandgit -C <receiver> worktree listnow, and compare them at the end (Done When). A difference means the run touched the original — say so. The copy exists to be thrown away.
(Confidential receivers were settled in Step 0. If you reached here with one, you are already in the owner's approved runtime.)
Step 2 — Run the receiver's OWN checks
Find how the receiver verifies itself. Look in its own CI config, package.json scripts, Makefile,
te