Skip to content

docs(agents): make question tool references environment-agnostic #8

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
TecFancy merged 1 commit into from
Mar 25, 2026
Merged

docs(agents): make question tool references environment-agnostic #8

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
4 changes: 2 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,9 +134,9 @@ Examples:

- **Language:** Thinking and response text follow the user's language. Code, comments, documentation, commit messages, and PR content are **always in English**.
- **Branch-first:** Always create a feature branch before writing any code — never commit directly to `main` or `development`.
- **Commit/PR review:** Before executing `git commit` or creating a PR, display the proposed message in the response text, then call `vscode_askQuestions` with confirm/edit/cancel options. Never execute without tool-based confirmation.
- **Commit/PR review:** Before executing `git commit` or creating a PR, display the proposed message in the response text, then ask the user for confirmation using the environment's question/ask tool (e.g., `vscode_askQuestions` in VS Code, `question` in opencode) with confirm/edit/cancel options. Never execute without tool-based confirmation. Use single-select for yes/no confirmations; use multi-select (`multiple: true` where supported) when the user needs to choose multiple items (e.g., files to stage, issues to fix).
- **Iterative workflow:** If new changes arise after a commit, re-enter the workflow from the appropriate step — assess, stage, show message, commit. Never skip steps.
- **Session end gate:** After completing any task or yielding control, **always** call `vscode_askQuestions` to ask the user about the next action. Include context-appropriate options and a "pause/stop" choice. This applies after every commit, push, PR creation, or code change — not only at session end.
- **Session end gate:** After completing any task or yielding control, **always** ask the user about the next action via the environment's question/ask tool. Include context-appropriate options and a "pause/stop" choice. This applies after every commit, push, PR creation, or code change — not only at session end.

## Important Constraints

Expand Down
Loading