luxtelos
@luxtelos Organization
Public Skills
loop-tick
by luxtelos
Advance the LoopKit pipeline by exactly one stage — a lookup over state/triage.md, never a judgement. Use for "work the backlog", "advance the pipeline", any /loop tick.
commerce-review
by luxtelos
The review checklist for a commerce agent — a shopping or merchant agent built on the commerce-agents blueprint. Use when the project has the commerce profile (loopkit-init.sh --profile commerce) and a change touches checkout, cart, refund, pricing, payout or a payment tool; use inside pr-review and acceptance-review for those diffs.
loop-assess
by luxtelos
Classify a finding before anyone writes a spec — establish the baseline, name the layer (measurement, code, tool, spec, process, architecture, prompt, decision), route it. Mode B audits an instruction file. Use on any new triage row, alert, complaint, or "tighten this CLAUDE.md".
memory
by luxtelos
Consult and record memory through the loop's adapters — structural code graph, episodic notes/palace, curated knowledge — instead of grep or RAG. Use when a change touches a storage invariant, a table, a past decision, or "has this bitten us before"; use before any migration; use to record a finding that must survive the session.
morning-triage
by luxtelos
Discovery — scan GitHub issues (and anything else the project names) for work, rank it, and append rows to state/triage.md at status new. Never modifies or closes existing rows.
acceptance-review
by luxtelos
Grade a change against its EARS acceptance criteria by ACTING — reproduce the trigger, observe the response, attach the evidence. PASS / FAIL / BLOCKED, never a rounded-up pass. Run by the Stop hook and by the reviewer.
loop-scan
by luxtelos
Deterministic status of what is in flight — open PRs, their real blockers, loop-owned issues, and the local triage backlog GitHub cannot see. Use for "what's open", "what can be merged", "what needs me".
pr-review
by luxtelos
One-shot review and verification of a single GitHub PR in an isolated worktree — tests, lint, acting on the changed behaviour, PASS/REJECT with evidence. Never merges, never approves.
spec-writer
by luxtelos
Turn a classified finding into a validated EARS spec in specs/ — outcome, scope, testable acceptance lines, edge-case families, and an inbox route for anything that needs a human number. Never overwrites an existing spec.
run-state-model
by luxtelos
Model-check a state machine before it becomes a spec — FizzBee, Quint/Apalache and TLA+ behind one driver with one honest exit-code contract (PASS / VIOLATION / ERROR / UNPROVEN). Use when a design has two writers, a retry, a guard-then-write, or a non-atomic step.