Accept positional body in os-backlog comment #421
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#421
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Agents pattern-match on tea/gh style (
tea comment 420 "body") and tryos-backlog comment 420 "text", which fails because the comment subcommand requires --body/--body-file. Seen repeatedly across sessions (screenshot reviewed 2026-08-16). Accept a positional body argument, keep --body/--body-file, and error only when more than one body source is given.Origin
os-backlog comment 420 "..."during /os-sdlc:implement #420 setupResolution
Done: os-backlog comment now accepts a positional body argument; --body/--body-file unchanged; errors when zero or multiple body sources are given.
Evidence: Commit
ce66705on branch worktree-sdlc+420; comment_cli_test.rb 9 runs / 33 assertions green (red-first), full os-backlog suite 203 runs / 0 failures.Follow-ups: Consider accepting a positional body for other body-taking subcommands (e.g. occurrence) if the same tea-style reflex bites there.