d37b2973b2
* add to event stream sync * remove async from tests * small logging spam fix * remove swe agent * arch refactoring: use history from the event stream * refactor agents * monologue agent * ruff * planner agent * micro-agents * refactor history in evaluations * evals history refactoring * adapt evals and tests * unit testing stuck * testing micro agents, event stream * fix planner agent * fix tests * fix stuck after rename * fix test * small clean up * fix merge * fix merge issue * fix integration tests * Update agenthub/dummy_agent/agent.py * fix tests * rename more clearly; add todo; clean up
1.3 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 first use git status to check whether it's a valid git repo and there
is diff in the staging area. If not, please call the reject action.
If it is a valid git repo and there is diff in the staging area, 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.
History
{{ instructions.history_truncated }} {{ history_to_json(state.history, max_events=20) }}
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 }}