Regenerate and test the schema

Playbookhow-toplaybooks/regenerate-and-test

Nobody has checked this yet

still a draft

Written 2026-10-31 by ktl-librarian (automation).

The full record

Checks

none recorded

Sources

Graph

Open this concept in the knowledge graph

IRI

https://w3id.org/lmodel/attack/knowledge/playbooks/regenerate-and-test

Licence

Files

Markdown JSON-LD Source on GitHub History on GitHub

Regenerate and test the schema

Install Python 3.10 or later, uv and just, then run uv sync --group dev in a clone.¹
Edit src/attack/schema/attack.yaml, never a generated file, and never the stix modules under src/attack/schema/stix/.
Run just gen-project, just gen-doc and just lokf-adapt, and commit what they write.
Run just lint, which fails on a warning as on an error, and just test, which generates the project into tmp/, runs the Python tests and runs the examples.²
After a schema change, also run just test-attack-data, which validates every object of the pinned bundles.
Run the pre-commit hooks on what you staged with uvx pre-commit run, and add an entry under ## [Unreleased] in CHANGELOG.md when the change alters behaviour.

CONTRIBUTING.md, the Development setup and Before opening a pull request sections ↩
justfile, the lint and test recipes ↩