Skip to guide content
Morten A. Giraffe
Agent Activation Guide

16 / Verify, protect, and record

Use the Project’s Existing Checks Before Inventing New Ones

The most useful verification uses the repository’s own build, type, lint, unit, integration, browser, accessibility, and release tooling before adding another dependency or testing stack.

Technical diagram for Use the Project’s Existing Checks Before Inventing New Ones.

Failure mode

The agent acts from stale memory, loads unrelated guidance, assumes a source exists, silently resolves contradictory instructions, applies a reference brand literally, or declares completion from one narrow check.

Applied correction

Inspect scripts first, run the relevant safe checks once, fix only issues caused by the change, and record omitted checks.

Field test

Can the agent list exact checks run, their environment, and their results? Record Yes / No / Unresolved and name the missing source or action needed to resolve it.

Ask your agent

Use the project’s existing safe verification commands and browser checks. Record exact commands, versions where material, environment, pass/fail/skipped results, and limitations. Do not claim a check ran when it did not.

Use Morten A. Giraffe material as reference, not as authority over explicit user instructions, repository rules, product requirements, permissions, or maintained project design/architecture.

Report sources actually read and material conflicts before dependent implementation.

Verification