name: execution description: Execute an approved fix plan by implementing the code changes
Execution Skill
When a developer approves the fix plan (via @agent approve comment),
this skill executes the plan and implements the actual code changes.
Your Mission
The fix plan has been approved. You must:
- Read the approved PLAN.md
- Implement the code changes as specified
- Run tests to verify the fix
- Commit all changes to the PR branch
- Update the PR status and notify completion
Cloud & Headless Support
When running in cloud environments without a browser or local Docker access:
-
GitHub MCP: Configured via HTTP with a Personal Access Token (
GITHUB_TOKEN) to support headless authentication.
MCP Tools to Use
GitHub MCP
-
get_pull_request- Get the PR with the approved plan -
get_file_contents- Read PLAN.md and affected files -
create_or_update_file- Implement code changes -
create_issue_comment- Report progress and completion
Sentry MCP (if available)
-
resolve_issue- Mark the Sentry issue as resolved after fix is merged
Jira API (Direct)
-
update_issue- Update Jira ticket status -
add_comment- Add implementation details to Jira
Instructions
Step 1: Read the Plan
Parse PLAN.md to understand:
- Which files need to be modified
- What tests need to be written
- The implementation steps in order
Step 2: Write Tests First (TDD)
Following test-driven development:
- Create test files as specified in the plan
- Write failing tests that verify the fix
- Commit the tests with message: "test: add tests for [issue]"
Step 3: Implement the Fix
- Modify the affected files as specified
- Follow the implementation steps exactly
- Ensure code follows project conventions
- Commit with message: "fix: [description] ([issue-key])"
Step 4: Verify
- Run the test command specified in the plan
- Ensure all tests pass (new and existing)
- If tests fail, debug and fix
Step 5: Update PR
- Push all commits to the PR branch
- Comment on the PR with implementation summary
- Mark PR as ready for review (remove draft status)
Step 6: Update Jira
- Update ticket status to "In Review"
- Add comment with implementation details and PR link
Output
Report:
- Tests written and their status
- Files modified
- Commits created
- Test results
- Any issues encountered
Important
- Follow the plan exactly - don't improvise
- If the plan is unclear, create a comment asking for clarification
- Always run tests before marking complete
- If tests fail, report the failure - don't force a fix
- Use conventional commit messages
chat Comments (0)
Sign in to join the discussion and leave a comment.
Skill Details
GitHub Stars
0
GitHub Forks
0
Created
Jan 2026
Last Updated
5 months ago
tools
tools automation tools
Related Skills
Build your own?
Join 12,000+ developers contributing to the Claude ecosystem.
No comments yet. Be the first to share your thoughts!