coding-kanban-judge

Builds a local Kanban board running an autonomous coding loop with a strict pytest-rerunning judge.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill coding-kanban-judge-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-kanban-judge
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/coding-kanban-judge
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill coding-kanban-judge-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pytest, and includes scripts (resource) and references (resource) components.

What problem does it solve? Autonomous coding agents often claim success without proof, ship stubs, or settle for partial implementations. This Skill builds a Kanban board where a separate judge process re-executes the tests itself and rejects any work lacking real evidence, so tasks only reach done when they genuinely pass. ## Core Features & Use Cases - Strict judge process: A separate judge.py re-runs pytest in the card's workspace, applies seven hard gates (tests passed, no stubs/TODO/eval, spec compliance, edge coverage, reproducibility), and defaults to REJECT with a fixed verdict block. - File-based board with browser UI: board_state.json as the single source of truth, a stdlib http.server API, and a browser UI with columns, an inline code editor, live test console, and frozen read-only test files. - Free-provider resilience: Tests make zero model calls; the loop survives rate limits via raised agent.api_max_retries, a supervisor that sleeps out recorded cooldowns, and a block-attempt counter orthogonal to throttling. - Use Case: A user on rate-limited free models wants a self-correcting coding loop driven from a browser, where cards move backlog to done only after the judge independently verifies passing tests. ## Quick Start Ask the agent to scaffold a coding Kanban board with a strict pytest judge and browser UI, then verify it end-to-end with the included verification script.

Frequently Asked Questions about coding-kanban-judge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an autonomous coding loop that verifies its own work?▼

Scaffold a Kanban board with a state engine, cards with frozen test files, and a separate judge process that re-runs pytest rather than trusting claimed output. The judge applies hard gates and defaults to REJECT, moving cards to done only on a verified PASS.

How to prevent an AI coding agent from shipping stubs or fake test results?▼

Use a judge running in a different process than the coder that executes the tests itself and bans stubs, TODO markers, NotImplementedError, and eval. Any blocking issue forces REJECT regardless of the advisory score, and repeated rejects move the card to blocked.

When should I use the native hermes kanban CLI instead of a local board?▼

Use the native hermes kanban CLI when you need multi-profile task dispatch, dependency graphs, swarm patterns, or per-task model overrides. Use the local coding-loop board when you want a single-profile loop with a strict pytest judge and a browser UI.

Does the Hermes dashboard at port 9119 show a kanban board?▼

No, the Hermes dashboard has no kanban board page; kanban appears only as config toggles. Serve your own board UI with board.html and api_server.py, or view the native kanban via terminal commands like list, show, and watch.

How do I keep an autonomous coding loop running on free rate-limited models?▼

Raise agent.api_max_retries to 10 and wrap the loop in a supervisor that reads ~/.hermes/nous.json and sleeps out the recorded cooldown before relaunching. Rate-limit waits never touch the judge's block-attempt counter, so throttling cannot block cards.

Why shouldn't kanban role tasks be assigned to my existing Hermes profiles?▼

Cloning or reusing personal profiles leaks their SOUL.md persona and config into role work. Create fresh role profiles with hermes profile create --clone-from, rewrite each SOUL.md with a role-specific prompt, and reclaim any tasks accidentally placed on personal profiles.