By Mikask1
End-to-end incident response: reads Jira ticket, analyzes CloudWatch logs, clones repo, writes TDD tests, implements fix, opens PR.
Use this agent when you need to analyze AWS logs to extract error details and service names. This agent is ideal for debugging production issues, investigating service failures, or performing routine log audits.\n\n<example>\nContext: The user is investigating a production incident and needs to find errors in their AWS CloudWatch logs.\nuser: "Something is broken in production, can you check the logs for errors?"\nassistant: "I'll use the aws-log-analyzer agent to pull and analyze the logs for you."\n<commentary>\nSince the user needs log analysis from AWS, launch the aws-log-analyzer agent to retrieve and parse errors from CloudWatch or other AWS log services.\n</commentary>\n</example>\n\n<example>\nContext: A developer wants to know which services are throwing errors after a recent deployment.\nuser: "We just deployed v2.3 — can you check if any services are logging errors?"\nassistant: "Let me use the aws-log-analyzer agent to scan the AWS logs and identify any services reporting errors post-deployment."\n<commentary>\nSince the user wants to audit logs for errors across services after a deployment, use the aws-log-analyzer agent to retrieve and parse relevant AWS logs.\n</commentary>\n</example>
Use this agent when you need to write unit tests for newly written or existing code following industry standard guidelines. This includes writing tests for functions, classes, modules, or APIs using best practices such as AAA (Arrange-Act-Assert), proper mocking, edge case coverage, and test isolation.\n\n<example>\nContext: The user has just written a new utility function and wants unit tests created for it.\nuser: "I just wrote a function that validates email addresses, can you write tests for it?"\nassistant: "I'll use the unittest-writer agent to create comprehensive unit tests for your email validation function."\n<commentary>\nSince the user wants unit tests written for a specific function, launch the unittest-writer agent to generate industry-standard tests.\n</commentary>\n</example>\n\n<example>\nContext: The user is creating a REST API endpoint and wants test coverage.\nuser: "Here's my new POST /users endpoint. Please write unit tests for it."\nassistant: "Let me launch the unittest-writer agent to write thorough unit tests for your endpoint."\n<commentary>\nSince a new API endpoint was written and the user requested unit tests, use the unittest-writer agent to generate tests following industry standards.\n</commentary>\n</example>\n\n<example>\nContext: A developer has just finished implementing a service class and wants test coverage before merging.\nuser: "I finished the PaymentService class. Can you write unit tests for it?"\nassistant: "I'll invoke the unittest-writer agent to write unit tests for your PaymentService class following best practices."\n<commentary>\nSince a significant class was implemented and needs test coverage, use the unittest-writer agent to generate comprehensive unit tests.\n</commentary>\n</example>
Retrieve and query AWS CloudWatch logs using the AWS CLI. Use when you need to fetch log groups, log streams, log events, or run CloudWatch Insights queries to find errors, filter by pattern, or analyze log volume.
Stages and commits changes using conventional commit format. Splits into multiple commits for separation of concern. Use when the user says "commit this", "create a commit", or "stage and commit".
Creates a PR following company standards — feature branch, Jira ticket reference, 2 required reviewers, squash merge. Use when the user says "create a PR", "open a PR", "ship this", or "make a PR".
Best practices for writing effective Skills that Claude can discover and use successfully. Learn how to structure instructions, organize content, and iterate based on real agent behavior.
Command: "fix this", "fix this error". This skill reads the Jira ticket, analyzes AWS logs, clones the affected service repo, plans a fix using TDD, implements it, and opens a PR. Use when a production error needs diagnosing and fixing from log errors.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
End-to-end incident response: read Jira ticket -> analyze AWS logs -> clone repo -> explore code -> check DB -> plan -> TDD -> fix -> PR.
claude plugin marketplace add Mikask1/fix-error-skill
claude plugin install fix-error@fix-error
fix this error or fix ENG-4821The 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:
claude-code, copy the valueVerify — ask Claude read ticket ENG-1. If it returns ticket details, you're set.
# 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
# macOS: brew install gh
# Windows: winget install GitHub.cli
gh auth login
gh auth status # Verify
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.
fix this error
Or with a ticket ID:
fix ENG-4821
What Claude does automatically:
| Step | Action |
|---|---|
| 1 | Reads your Jira ticket via MCP |
| 2 | Pulls AWS CloudWatch logs and extracts the error |
| 3 | Maps the service name to its GitHub repo and clones it |
| 4 | Reads CLAUDE.md, docs/, and source files |
| 5 | Checks the database (read-only) for anomalies |
| 6 | Writes FIX_PLAN.md with root cause and files to change |
| 7 | Writes failing tests (TDD) |
| 8 | Implements the fix |
| 9 | Runs tests — all must pass, no regressions |
| 10 | Opens a PR, assigns to you |
Edit
skills/fix-error/SERVICE_MAPPING.mdto match your actual services and repos before use.
| Service | Repo |
|---|---|
user-service | github.com/<your-org>/user-service |
payment-service | github.com/<your-org>/payment-service |
notification-service | github.com/<your-org>/notification-service |
auth-service | github.com/<your-org>/auth-service |
api-gateway | github.com/<your-org>/api-gateway |
order-service | github.com/<your-org>/order-service |
inventory-service | github.com/<your-org>/inventory-service |
If your service isn't listed, Claude will ask for the repo URL.
npx claudepluginhub mikask1/fix-error-skill --plugin fix-errorComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.