anchors check

Run the quality gates (the pipeline).

Confronts the nodes against the quality gates declared in anchors.yaml
and reports the verdict profile (QUALITY §5-§6).

By default it is INCREMENTAL: it runs over the impact path of a changed file
(--changed <file>). With --all, it sweeps every node (expensive; the full picture).

Each gate that fails generates an issue; a blocking gate that fails bars
promotion. Informative gates enter the profile but do not bar (maturation, §7).

--deterministic SKIPS the AI judgment gates (measures: judgment) and runs only
the computable ones. It is the PRE-COMMIT mode: a judge gate cannot bar a commit
(there is no waiting for the AI) nor should it queue judgment on every commit (repeated
garbage). Without that mode, judge becomes invisible (it neither bars nor records).

Uso

anchors check [flags]

Flags

Flag	Padrão	O que faz
--all		scan every node (the full picture; expensive)
--category		enforces only the gates of this nature (types|style|traceability…)
--changed		changed file(s) — repeatable or comma-separated; the gates run ONCE over the union of the impact paths
--commit-msg		path to the commit message file, from which to read the [skip-<gate>@<CODE>: reason] markers
--deterministic		runs only the computable gates (skips the AI-judgment ones) — the pre-commit mode
--fix		self-healer: applies the automatic repairs (e.g. fixes updated_at) before confronting
--index		the gates read the files as the git index has them — what the commit records (the pre-commit mode)
--map		path to the map
--no-record		report only: neither stamps the map nor opens issues
--only-issues		omits from the table the gates that passed everything and left no pending item (the total remains in the footer)
--phase		enforces only the gates of this phase (pre-commit|pre-push|ci|manual)
--record-issues		github mode: open/close board issues from a local run too (by default only CI does); manual mode: write the issues to issues/ (by default none is written)
--root	.	project root
--show-drift		lists ALL the pending items (⚠) with the address of each one; without the flag, only the table counter
--skip-rule		waives rules in this run: id=reason[,id=reason]. The reason is mandatory
--skip-slow		skip gates declared cost: slow
--timing		measures how long each gate took, and names the slowest targets — to find what makes a scan expensive

Confronto do projeto — família

Comandos da mesma família — o que distingue cada um:

Comando	O que faz
anchors check	Run the quality gates (the pipeline)
anchors verify	Run EVERYTHING the phase requires: Anchors gates + external tools
anchors coverage	Show coverage by scenario, by line, of the DIFF and the delta
anchors stale	List stale edges — what changed and has not been reconfronted
anchors impact	Impact analysis: what a change to this file reaches
anchors failures	The observed failures that the spec has not yet explained

---

---

---

---

---

O comando anchors check é o motor central de verificação do Anchors. Ele avalia os gates de qualidade configurados contra os arquivos alterados, em stage ou em todo o repositório.

---

1. Sintaxe e Opções Comuns

# Verifica arquivos modificados no diretório de trabalho
anchors check

# Verifica arquivos em stage (usado pelo hook pre-commit)
anchors check --staged

# Verifica todos os arquivos regidos do projeto inteiro
anchors check --all

# Roda apenas um gate específico
anchors check --gate=unit-complete

# Roda em modo estrito (falha se houver avisos/warnings)
anchors check --strict

Códigos de Saída (Exit Codes):

• 0: Todos os gates passaram com sucesso (OK).
• 1: Um ou mais gates bloqueantes retornaram FAIL.
• 2: Erro de configuração ou leitura de arquivos.

---

2. Diferença entre check e verify

• anchors check: Avalia os gates internos do Anchors (completude de unidade, códigos de identidade, fronteiras arquiteturais, paridade de docs).
• anchors verify: É o orquestrador da fase completa. Ele roda anchors check, executa as suítes de teste do projeto (anchors test), dispara linters externos e checa mutação antes de aprovar uma entrega.

---

3. Exemplo na Esteira de CI/CD

- name: Avaliar Gates do Anchors
  run: anchors check --all