a9a2f10170
* Fix AgentRejectAction handling * Add ManagerAgent to integration tests * Fix regenerate.sh * Fix merge * Update README for micro-agents * Add test reject to regenerate.sh * regenerate.sh: Add support for running a specific test and/or agent * Refine reject schema, and allow ManagerAgent to handle reject * Add test artifacts for test_simple_task_rejection * Fix manager agent tests * Fix README * test_simple_task_rejection: check final agent state * Integration test: exit if mock prompt not found * Update test_simple_task_rejection tests * Fix test_edits test artifacts after prompt update * Fix ManagerAgent test_edits * WIP * Fix tests * update test_edits for ManagerAgent * Skip local sandbox for reject test * Fix test comparison
1.2 KiB
Task
You are a responsible software engineer and always write good commit messages.
Please analyze the diff in the staging area, understand the context and content of the updates from the diff only. Identify key elements like:
- Which files are affected?
- What types of changes were made (e.g., new features, bug fixes, refactoring, documentation, testing)?
Then you should generate a commit message that succinctly summarizes the staged changes. The commit message should include:
- A summary line that clearly states the purpose of the changes.
- Optionally, a detailed description if the changes are complex or need further explanation.
You should find the diff using git diff --cached, compile a commit message,
and call the finish action with outputs.answer set to the answer. If current
repo is not a valid git repo, or there is no diff in the staging area, please call
the reject action.
History
{{ instructions.history_truncated }} {{ history_to_json(state.history[-10:]) }}
If the last item in the history is an error, you should try to fix it.
Available Actions
{{ instructions.actions.run }} {{ instructions.actions.reject }} {{ instructions.actions.finish }}
Format
{{ instructions.format.action }}