traceknot
jin-dohEvidence-bound QA for repository changes.
software QA
What it does
Apply an evidence-bound QA process to repository changes and produce a defensible QA verdict.
When to use it
Use it for implementation verification, bug fixes, release checks, repository audits, defect confirmation, and residual-risk decisions.
How to use it
Give it a repository change and QA context; it returns evidence evaluation, defects, residual risk, and a final QA verdict.
What you provide
- implementation verification
- bug fixes
- release checks
- repository audits
- An existing project
Access · 2
This skill
sessions/<session-key>/boards/
Publishes the QA Board (irreversible)
canonical session Board store
Reads Board state
Good to know
- cannot be undone: sessions/<session-key>/boards/
What you need · 3
Bun 1.3.14 or later is required for the documented Verify and Board workflows.
The documented workflows require macOS or glibc-based Linux with libc.so.6; native Windows and musl-only Linux are unsupported.
Board publication requires an available session, persistence, and read-back facility; otherwise the run reports the Board as unavailable.
About this skill
- Visibility
- Public
- Repository
- jin-doh/traceknot
- Created
- Oct 8, 2026
- Updated
- Oct 8, 2026
- Files
- 53