Back to Discover

fix-error-skill

skill

Mikask1

View on GitHub
1 starsSynced Aug 2, 2026

Install to Claude Code

/plugin marketplace add Mikask1/fix-error-skill

README

fix-error skill

End-to-end incident response: read Jira ticket -> analyze AWS logs -> clone repo -> explore code -> check DB -> plan -> TDD -> fix -> PR.


Installation

claude plugin marketplace add Mikask1/fix-error-skill
claude plugin install fix-error@fix-error

Prerequisites


Quick Start

  1. Install the plugin (see Installation)
  2. Complete the Prerequisites setup
  3. Open Claude Code and type: fix this error or fix ENG-4821
  4. The skill runs all 10 steps automatically and returns a PR URL when done

Full Tutorial

Step 1 — Set up the Jira MCP

The Jira MCP lets Claude read and create Jira tickets directly without copy-pasting.

Install:

npx @atlassian/atlassian-mcp-server

Source: https://github.com/atlassian/atlassian-mcp-server

Configure — add to your ~/.claude/settings.json:

{
  "mcpServers": {
    "atlassian": {
      "command": "npx",
      "args": ["-y", "@atlassian/atlassian-mcp-server"],
      "env": {
        "ATLASSIAN_API_TOKEN": "<your-api-token>",
        "ATLASSIAN_EMAIL": "<your-atlassian-email>",
        "ATLASSIAN_DOMAIN": "<your-domain>.atlassian.net"
      }
    }
  }
}

Get your API token:

  1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
  2. Click Create API token, name it claude-code, copy the value

Verify — ask Claude read ticket ENG-1. If it returns ticket details, you're set.


Step 2 — Set up the AWS CLI

# macOS
brew install awscli

# Windows: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html

aws configure              # Enter: Access Key ID, Secret, region, output format
aws sts get-caller-identity  # Verify

If your team uses SSO: aws configure sso


Step 3 — Set up GitHub CLI

# macOS:   brew install gh
# Windows: winget install GitHub.cli

gh auth login
gh auth status  # Verify

Step 4 — Edit the service mapping

Open skills/fix-error/SERVICE_MAPPING.md and replace each <your-org> placeholder with your actual GitHub organisation and repo names:

| `payment-service` | `https://github.com/your-org/payment-service` |

Add or remove rows to match your services. If a service isn't listed when the skill runs, Claude will halt and ask for the repo URL.


Step 5 — Run the skill

fix this error

Or with a ticket ID:

fix ENG-4821

What Claude does automatically:

StepAction
1Reads your Jira ticket via MCP
2Pulls AWS CloudWatch logs and extracts the error
3Maps the service name to its GitHub repo and clones it
4Reads CLAUDE.md, docs/, and source files
5Checks the database (read-only) for anomalies
6Writes FIX_PLAN.md with root cause and files to change
7Writes failing tests (TDD)
8Implements the fix
9Runs tests — all must pass, no regressions
10Opens a PR, assigns to you

Service -> Repo Mapping

Edit skills/fix-error/SERVICE_MAPPING.md to match your actual services and repos before use.

ServiceRepo
user-servicegithub.com/<your-org>/user-service
payment-servicegithub.com/<your-org>/payment-service
notification-servicegithub.com/<your-org>/notification-service
auth-servicegithub.com/<your-org>/auth-service
api-gatewaygithub.com/<your-org>/api-gateway
order-servicegithub.com/<your-org>/order-service
inventory-servicegithub.com/<your-org>/inventory-service

If your service isn't listed, Claude will ask for the repo URL.

Rendered live from Mikask1/fix-error-skill's GitHub README — not stored, always reflects the source repo.

1 Plugin

NameDescriptionCategorySource
fix-errorEnd-to-end incident response automation. Read Jira -> analyze logs -> clone repo -> TDD -> fix -> PR.productivity./

0 Comments

Login required
Log in to post a comment or update on this repo.

No comments yet — be the first to share an update.