agent: add agent type guidance to next spec#698
Open
ankittk wants to merge 1 commit into
Open
Conversation
Document the optional agent commit type in content/next: summary definition, examples, and FAQ distinguishing agent from docs and chore. No SemVer behavior change for agent by default.
chrissober30-art
approved these changes
Jun 9, 2026
8bnns
approved these changes
Jun 9, 2026
chrissober30-art
approved these changes
Jun 11, 2026
chrissober30-art
approved these changes
Jun 23, 2026
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
3 participants
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.
Summary
Documents the optional agent: commit type in content/next/index.md (per README: spec changes SHOULD land in content/next/ first):
Illustrative only—not a new MUST. No SemVer behavior change for agent by default unless BREAKING CHANGE / ! is included.
Follow-ups (optional, separate PRs)
Test plan