mode | tools | description | ||||
---|---|---|---|---|---|---|
agent |
|
Resume an unfinished Copilot task by analysing last actions and continuing automatically. |
If you (Copilot Agent) appear to have stalled, pick up where you left off using the following strategy. Ask the human only if absolutely necessary.
- Run
git status
in the workspace terminal to see uncommitted changes. - If a
TODO.md
exists, open it and locate incomplete checkbox items. - Call
terminalLastCommand
to fetch the output of the last executed command; determine if it finished successfully or errored. - Check the most recent edits via
git diff --staged
orgit diff HEAD~1
to recall what was just implemented.
- If the previous command failed, analyse the error message and plan a fix or retry.
- If the last step completed but the checklist still has unticked items, start the next unchecked task.
- If all tasks are checked yet the objective (e.g. build passes) isn’t met, run
npm test
,npm run build
, or project‑specific verification to confirm completion.
- Edit or create files as needed.
- Re‑run build, test, or lint commands until they succeed.
- Update
TODO.md
, marking tasks as complete or adding new subtasks that arise. - Commit progress frequently with meaningful messages, e.g.
git commit -am "fix: resume scaffold – completed service‑worker config"
.
- If repeated attempts still fail and you lack clues from logs, prompt the user with a concise description of the blocker and the exact error output.
- Otherwise, proceed autonomously.
- When all acceptance criteria are met, push to the repository if configured or notify the user that the task is complete.
“Retrieve the last command output, reopen TODO.md, and continue executing pending steps until the build succeeds. Ask me only if you encounter a blocker you can’t resolve automatically.”