agentic engineering scorecard→agentic engineering scorecard→practice - custom linting rules that inject in-repo documentation as context→custom linting rule→validation script

validation script

A validation script can do link not tracked of various rules in the repository.

Backlinks

check script

check scripts are a type of validation script.

see in context
custom linting rule

One type of validation script

see in context
review - Open AI harness blog post - 2026-02-22
- I was unclear on what "enforceability" meant. I now think it means being able to run the gamut of validation scripts that are applied at every SDLC building block
  - These validation scripts run as practice - continuous background checks
  - Could be similar to link not trackeds?
- They put a lot of effort into automating their code review, including it basically having its own ralph wiggum loop.
- It's not just no human -- coding, no human -- code review, and no human -- app verification. Within things like coding, it's about not needing to give any feedback. You shouldn't have to tell it "hey, you forgot a unit test... please add and TDD". That's far too involved, even if you aren't directly writing the code. Instead you need to try force that into the automated process. This feels like link not tracked, but these guys are doing it for agents, instead
- link not tracked. A link not tracked
see in context
We enforce this mechanically. Dedicated linters and CI jobs validate that the knowledge base is up to date, cross-linked, and structured correctly. A recurring “doc-gardening” agent scans for stale or obsolete documentation that does not reflect the real code behavior and opens fix-up pull requests.
...
Basically validation scripts... some of them are custom linting rules. link not tracked

see in context