Public Agent Skills by riekelt on Lightlines.
Maps the real code and data before changes or conclusions, quoting evidence for load-bearing claims.
Turns structural invariants into named contracts with written rationales and mechanical guards.
Reviews committed specs or plans with parallel reviewers, adjudication, and a gated verdict before execution.
Governs non-trivial engineering work with evidence, safety rules, and verification so changes remain true and safe.
Diagnoses technical prose by naming defects and applying the smallest edit that fixes each one.
Shapes technical documents around verified claims, clear structure, and a consistent house style.
Verifies changed code at its runtime surface and reports completion only from checked evidence.
Use meaningful completed work to produce changelog entries, release notes, or what-shipped summaries with defined structure and honesty conventions.
Shape proposals, RFCs, design documents, specifications, and migration plans into discussable documents with explicit reasoning, costs, and completeness checks.
Writes operational documentation that operators can execute safely under time pressure.
Shapes unit tests around behavioral contracts, deterministic setup, and visible failure claims.