auto-merge
01Skill Claude CodeCodex
Use when an explicitly authorized VHK maintenance session must evaluate open pull requests carrying the auto-merge label.
not rated 12 yesterday A 25 tokens
original MIT
12Stars on the repository
19Mods indexed here, across every type
yesterdayLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown
Skill Claude CodeCodex
Use when one VHK goal should run unattended overnight and stop after opening a pull request without merging.
not rated 12 yesterday A 26 tokens
original MIT
vhk-auto
03Skill Claude CodeCodex
Use when one active VHK goal should run autonomously through implementation and verification without external publication or merge.
not rated 12 yesterday A 25 tokens
original MIT
Skill Claude CodeCodex
A setup procedure for adding VHK to a Cursor project and connecting shared agent skills, project rules, session hooks, and verification steps.
not rated 12 yesterday A 30 tokens
original MIT
Skill Claude CodeCodex
A procedure for reproducing, classifying, and optionally reporting defects in the VHK command-line tool or its supporting setup.
not rated 12 yesterday A 38 tokens
original MIT
Skill Claude CodeCodex
A VHK improvement workflow that turns recorded lessons and successes into proposed project rules. VHK is a command-line tool for tracking development work, verification, and project guidance.
not rated 12 yesterday A 29 tokens
original MIT
vhk-gate
07Skill Claude CodeCodex
A completion checklist that runs VHK's verification, receipt, and review checks in order. A receipt records whether the current work was checked against the right project state.
not rated 12 yesterday A 26 tokens
original MIT
Skill Claude CodeCodex
A repair guide for VHK Goal files, which are small project records describing work to do and its status. It diagnoses invalid formats and restores only the files that are actually broken.
not rated 12 yesterday A 36 tokens
original MIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: