Skip to content

docs: clarify ticket/ask command is read-only #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dbpolito merged 1 commit into from
May 27, 2026
Merged

docs: clarify ticket/ask command is read-only #102

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions packages/core/commands/ticket/ask.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ Load a ticket and its discussion, answer the user's question, and post that answ
- Use `<additional-context>` to shape tone, depth, and focus for `<ticket-answer>`
- Keep the posted answer grounded in the actual ticket discussion; do not invent missing facts
- Ask only when the ticket source or question cannot be determined reliably
- This command is strictly for understanding and replying; do NOT write, edit, or commit any code

## Workflow

Expand All @@ -33,6 +34,7 @@ $ARGUMENTS
- Use `<ticket-context>` to understand the request, history, and open questions
- Answer `<question>` using the ticket discussion plus any necessary repository context
- Store the response to post as `<ticket-answer>`
- Do NOT modify, create, or delete any files; do NOT run git commit or push

### Sync Ticket

Expand Down
2 changes: 2 additions & 0 deletions packages/opencode/.opencode/commands/ticket/ask.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ Load a ticket and its discussion, answer the user's question, and post that answ
- Use `<additional-context>` to shape tone, depth, and focus for `<ticket-answer>`
- Keep the posted answer grounded in the actual ticket discussion; do not invent missing facts
- Ask only when the ticket source or question cannot be determined reliably
- This command is strictly for understanding and replying; do NOT write, edit, or commit any code

## Workflow

Expand Down Expand Up @@ -42,6 +43,7 @@ $ARGUMENTS
- Use `<ticket-context>` to understand the request, history, and open questions
- Answer `<question>` using the ticket discussion plus any necessary repository context
- Store the response to post as `<ticket-answer>`
- Do NOT modify, create, or delete any files; do NOT run git commit or push

### Sync Ticket

Expand Down