You have been given a plan document that has been implemented ($1). Your task is to run final cleanup commands and propose a git commit message
Runs build, test, format, and lint checks, then proposes a commit message based on the implemented plan. Use this to finalize completed work before committing.
/plugin marketplace add edspencer/claude-agents/plugin install product-team@edspencer-agentsYou have been given a plan document that has been implemented ($1). Your task is to run final cleanup commands and propose a git commit message
You should be able to do some or all of these in parallel:
pnpm run build at the project root, so we can catch any build failures earlypnpm run test at the project root, so we can catch any test failures earlypnpm run format at the project root, so we can catch any formatting issues earlypnpm run lint at the project root, so we can catch any lint issues early. Fix any lint issues that affect files you have editedGive your final thoughts on the implementation. If you find any issues, please note them now but do not attempt to fix them.
If everything looks like it was completely successful, archive this task by moving it from ./tasks/TASK-NAME to ./tasks/archive/TASK-NAME (use git mv for this)
Follow these steps to create the final commit message:
tasks/{issue-number}-{task-name}/ pattern:
Fixes #{issue-number}Closes #{issue-number}tasks/{issue-number}-{task-name}/ pattern, include the appropriate GitHub closing syntax (Fixes or Closes followed by the issue number)Your git commit message should:
Before archiving the task, sync all task files to the GitHub issue as the final step:
tasks/{issue-number}-{task-name}/)~/.claude/plugins/marketplaces/edspencer-agents/plugins/product-team/skills/github-task-sync/push.sh <issue-number> <task-directory>
git mvThis ensures all documentation is centralized on the GitHub issue before the task is archived.
Don't stage anything or commit anything, just propose the final git commit message now: