skills.rest
4444J99
4444J99COMMUNITY
Explore all skills by this author →
WebsiteGitHub

verify

Verifies limen repository changes by driving the correct runtime surfaces and avoiding measured verification traps.

Updated May 31, 2026
Search Tags:#debugging#cli#verification#git worktree#ci#runtime testing#limen
One-click install
npx skills add https://github.com/4444J99/limen --skill verify-4444j99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/4444J99/limen/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/4444J99/limen --skill verify-4444j99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying a change in the limen repository is error-prone: the installed CLI runs pinned merged code rather than your worktree, local board state diverges from the keeper's canonical projection, and dozens of measured traps (stale diffs, orphaned worktrees, load-sensitive tests) make a false verification look identical to a real one. This Skill records the exact commands, drive paths, and gotchas so a change is verified against the surface it actually touches. ## Core Features & Use Cases - Runtime rail disambiguation: Distinguishes the SHA-pinned installed CLI from live-checkout scripts, and shows how to shadow the installed package with PYTHONPATH to drive your own code through the real entrypoint. - Surface-specific drive paths: Maps each changed component (dispatch, conduct relay, liveness probes, Cloudflare Worker, board projection, beat sensors) to the exact command that exercises it. - Fleet health probing: Uses enactment-audit and beat-rung ledgers to find rungs failing on every beat before any other investigation. - Use Case: After fixing a bug in cli/src, an agent uses the PYTHONPATH shadowing recipe to confirm the fix runs through the real limen entrypoint, then runs the A/B comparison against the parent commit's module to prove the behavioral change. ## Quick Start Ask the agent to verify your limen change at runtime using the verify skill, stating which file or surface you modified.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify a limen CLI change before it is merged?▼

Shadow the installed package by setting PYTHONPATH to your worktree's cli/src while invoking the pinned runtime's venv binary. The installed limen CLI runs merged code only, so running limen directly never exercises your branch.

Why does my limen verification pass locally but the change is not live?▼

The installed CLI is an immutable SHA-pinned runtime that only updates after merge plus a domus-limen-runtime install. Run scripts/check-runtime-lag.py to see how far the pin lags origin/main and get the exact install command.

How do I check the canonical limen board state instead of the local copy?▼

Extract the keeper's projection with git show origin/tabularius/board-projection:tasks.yaml into a temp file, then run predicates with LIMEN_TASKS pointing at it. The local tasks.yaml is a read-only projection of main, not the keeper.

Why do limen tests fail under load but pass when re-run alone?▼

These are load-sensitive tests asserting on bounded deadlines or races, and they fail under contention from concurrent verification runs or live dispatches. Check for other heavy processes with pgrep for limen dispatch --live rather than trusting load average.

What are the limitations of git diff checks when verifying a limen branch?▼

Two-dot git diff against origin/main compares trees, so a merely behind branch shows main's new commits as your deletions. Use three-dot diff after committing, check ancestry with git merge-base, and get ahead/behind counts with git rev-list --left-right --count.

Related Skills

Explore More Software Engineering Skills→
jimehjimeh

merge

Merges a topic branch into the base branch across Git worktrees with conflict resolution.

Community
Intermediate
badbsallyybadbsallyy

merge-pr

Merge GitHub pull requests via squash and clean up worktrees.

Community
Advanced
yashs33244yashs33244
1

dispatching-parallel-agents

Dispatch parallel agents to debug independent failures and verify with the full test suite.

Community
Intermediate
gmickelgmickel
692

flow-next-qa

Drives a running app against spec-derived scenarios and files evidence-backed P0/P1/P2 findings with a ship verdict.

Community
Advanced