docs: clarify agent workflow and branch naming rules - #163
Merged
Merged
Conversation
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.
Change
Clarify
AGENTS.mdso new branches use purpose-based names such asfeat/*,fix/*, anddocs/*, with lowercase kebab-case descriptions. Explicitly exclude agent/tool prefixes such ascodex/, while respecting a branch name explicitly requested by the user.Correct the distinction between Vitest and Node test registration, document source-export prerequisites and verification profile selection, and clarify inventory regeneration and public-source review boundaries. Only
AGENTS.mdchanges.Validation
pnpm verify: all 14 gates passed on macOS arm64, Node.js 26.4.0, full profile, revision596856e1a660e0a72fce48780311ca85e82b0b7f.git diff --check: passed.AGENTS.mdchanges select full CI under the existing change classifier.Publication and contribution checks
release/public-source.json; new tests are declared intest/vitest-suites.jsonwhere applicable. No files or tests were added or removed; no regeneration was needed.Maintainer handoff
Publication scope or license changes: none.
Shared-source port: not needed; this updates public-repository agent guidance only.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.