القائمة
Verify Arborchive changes using the project verification spec, choosing docs-only, behavior, schema, database, and build checks based on the change type.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Finish an Arborchive task with a concise review-ready summary covering changed files, changes made, commands, verification result, risks, follow-ups, and commit message.
Orient an agent at the start of an Arborchive task by loading governance docs, Trellis-style context docs, and the relevant Arborchive specs before planning or editing.
Create a lightweight Arborchive implementation plan with scope, non-goals, allowed paths, forbidden paths, required specs, validation plan, and risks before editing.
Review Arborchive schema and CodeQL alignment changes for table category, counterpart semantics, extension rationale, validation query, migration impact, and tests.
| name | arborchive-verify |
| description | Verify Arborchive changes using the project verification spec, choosing docs-only, behavior, schema, database, and build checks based on the change type. |
Use this skill after changes and before final reporting. Follow
.trellis/spec/arborchive/testing-and-verification.md.
Run:
git diff --check
git status --short
git diff --name-only
Explain why behavior tests are not required when no code, schema, build, or fixture files changed.
Run the relevant checks:
scripts/test_all.sh
When semantic output changes, inspect generated database output as needed:
python3 scripts/db_summary.py tests/output/<case>.db
sqlite3 tests/output/<case>.db ".tables"
sqlite3 tests/output/<case>.db "select * from <table> limit 10;"
For schema or ORM changes, consider the full path:
python3 scripts/generate_instantiations.py
make debug -j 8
scripts/test_all.sh
Always report:
Do not claim completion when required checks fail or could not run.