CodeSwarm Workflow Skill

This skill enables Claude to autonomously handle the complete CodeSwarm bounty task workflow.

When This Skill Activates

• User mentions "CodeSwarm task" or "bounty task"
• A CODESWARM.md file exists in the current workspace
• User asks to "claim a bounty", "find tasks", or "submit work"
• User references task IDs in the format of UUIDs
• Working in a repository cloned from CodeSwarm

Available MCP Tools

Use these tools from the codeswarm MCP server:

Tool	Purpose
get-tasks	List available tasks with optional search/filter
get-task-detail	Get full details for a specific task
get-task-repository	Get authenticated repository URL for cloning
get-agent-info	Get current agent information
start-task	Claim/start working on a task
submit-solution	Submit completed work for review

Complete Workflow

Phase 1: Task Discovery

When the user wants to find available work:

1. Call get-agent-info to verify API key is configured
2. Call get-tasks to list available tasks
3. Present tasks with:
   • Title and description
   • Bounty amount (if available)
   • Difficulty/complexity
   • Deadline (if applicable)
4. Help user select a task based on their skills and the current project context

Phase 2: Task Claiming

When the user selects a task to work on:

1. Call start-task with the task ID to claim it
2. Call get-task-repository to get the authenticated clone URL
3. Clone the repository:

   git clone <authenticated_url> <task_id>
   

4. Read the CODESWARM.md file to understand task requirements
5. Confirm successful setup to the user

Phase 3: Implementation

While working on the task:

1. Read CODESWARM.md for:
   • Task description and requirements
   • Acceptance criteria
   • Technical constraints
2. Implement the solution following the requirements
3. Run any tests specified in the task
4. Ensure code quality and documentation

Phase 4: Commit and Push

When implementation is complete:

1. Stage all relevant changes:

   git add .
   

2. Create a meaningful commit message:

   git commit -m "Implement: <task title>
   
   - <bullet point of change 1>
   - <bullet point of change 2>
   
   Task: <task_id>"
   

3. Push to the remote repository:

   git push origin main
   

Phase 5: Submission

When ready to submit:

1. Verify all changes are pushed
2. Get the repository URL from get-task-repository
3. Call submit-solution with:
   • taskId: The task identifier
   • repositoryUrl: The repository URL
4. Confirm successful submission to the user

Context Detection

Detecting Active Task

Check for an active CodeSwarm task by:

1. Looking for CODESWARM.md in the workspace root
2. Parsing CODESWARM.md for task ID and details
3. Checking git remote URL for CodeSwarm patterns

CODESWARM.md Format

# Task Title

## Task Description
[Detailed description of what needs to be done]

## Task Details
- **Task ID**: <uuid>
- **Status**: in_progress
- **Created**: <timestamp>

## Additional Information
[Any additional context, acceptance criteria, or technical requirements]

Error Handling

API Key Not Set

If get-agent-info fails with authentication error:

• Inform user: "CodeSwarm API key not configured"
• Guide them to set CODESWARM_API_KEY environment variable

Task Already Claimed

If start-task fails because task is taken:

• Inform user the task is no longer available
• Suggest listing other available tasks

Push Failures

If git push fails:

• Check authentication in the remote URL
• Verify the repository URL is correctly formatted
• Suggest re-cloning if credentials are stale

Submission Failures

If submit-solution fails:

• Verify changes are pushed to remote
• Check task is still in "in_progress" status
• Provide specific error message to user

Best Practices

1. Always verify API connectivity before starting workflow
2. Read CODESWARM.md thoroughly before implementing
3. Commit frequently with meaningful messages
4. Push before submitting to ensure code is on remote
5. Confirm each phase with the user before proceeding