Task Handoff Verifier
Related Servers
Alternatives to Task Handoff Verifier
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables verification of AI coding agent self-reports against git diff truth and a deterministic gate, producing pass/regenerate/reject directives to ensure claimed work matches actual changes.6AGPL 3.0
- AlicenseAqualityCmaintenanceEnables AI coding agents to submit work for external review before declaring a task done, receiving evidence-backed fix lists and verdicts based on git-measured changes and calibrated quality scoring.3MIT
- AlicenseAqualityCmaintenanceAudits coding agents' claimed actions against the actual Git working tree, blocking completion if any claimed changes are unverified.2MIT
- AlicenseAqualityAmaintenanceFail-closed merge gate for AI coding agents: verify_repo runs the tests that existed before the change against a git working tree and answers MERGE, BLOCK or INCONCLUSIVE. The agent names what to judge; the operator pins the baseline and the floors.21,307 PyPI4AGPL 3.0
- AlicenseAqualityBmaintenanceChecks what local coding agents such as Claude Code, Codex and Cursor really did: files changed, commands run and test results read from test output, not the agent's word. Unclear test results can be double-checked by Laya (on your computer) or TypeSafe's Jev (cloud, your own API key). Read-only.21074 npm47MIT
- AlicenseNot gradedqualityBmaintenanceEnables an external AI agent to delegate tasks to a local Claude Code installation and receive structured reports, with code modifications governed by a plan-approval-execution workflow and direct file and git operations available outside that loop.MIT
TDQS
Scored across 8 tools
Most tools target distinct phases (setup, discovery, baseline, inspection, verification reporting), but verify_task's full pipeline overlaps with the combined inspect_task_state + run_relevant_checks, and summarize_handoff vs inspect_task_state vs verify_task all touch reporting similarly. Descriptions do distinguish them, so an agent can usually choose correctly.
All eight tools use consistent snake_case with a leading verb (open_, check_, find_, inspect_, run_, start_, summarize_, verify_). No camelCase or style mixing, and the pattern is predictable.
Eight tools is well-scoped for a task-handoff verification workflow, with each tool earning its place across discovery, setup, baseline, inspection, checks, and reporting.
The surface covers the full lifecycle: discovery (find_repos), environment (check_setup), baseline (start_task), inspection (inspect_task_state), checks (run_relevant_checks), and verification/reporting (verify_task, summarize_handoff, open_dashboard). Minor gaps like explicit baseline reset or history beyond the last report are workable given start_task overwrites baselines.