Repository navigation
docs(agents): sync agent skills and feature maps with 0.15.0 - #145
Merged
Merged
Conversation
Fix the 32 gaps from the agent-docs audit: the approval.md drive that left the clone memory at two-person, the pull-request.md doctor jq path, the approval-gate review seam, fixture approval notes in verify-venfork, and stale flag, error-code, help and CLAUDE.md text.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The agent docs lagged the 0.14.0 DX stack and the 0.15.0 approval gate. The worst gap: approval.md's drive (
stage approval on, thenoffwithout a TTY) leaves the clone memory attwo-person, so every later non-TTY stage in the fixture exits 1 withgate-weakened. pull-request.md'sjq .links.pulledPrsprintednull. Other stale text:--yesonpull pr, the help strings, thepreserverename, the README "JSON output" pointer, branch-only flags, error codes, refusal reasons, result shapes, the CLAUDE.md command checklist, the verify and managed-commit lists, and the PR template.This PR fixes all 32 audit gaps. It adds a reset step (
rm .git/venfork/approval.json) and fixture drives for a raised level and--force. It adds an approval-gate seam to review-venfork, approval notes to the verify-venfork SKILL.md, and a gotcha. CLAUDE.md now says venfork-config stores only the level. No gap was dropped. I adjusted three: H1 points athelp exit-codes, approval.md keepsjson-output, and setup needed no new test file.Possible follow-up, not fixed: the non-GitHub
preconditionhintvenfork stage approval offleads a non-TTY user intogate-weakened.bun run verifypasses. I drove the approval,--force, doctor andpull pr --yesrecipes on a fixture through a script file, because sourcing vf.env is blocked.Not verified: e2e tiers; the How to drive it recipes were not all run end to end; vf_yes TTY paths were not run.