Back to Skills

error-handler

verified

Standardized error responses for all failure scenarios. Always transparent, always provide next steps.

View on GitHub

Marketplace

development

JuniYadi/claude-code

Plugin

issue-reviews

productivity

Repository

JuniYadi/claude-code

issue-reviews/skills/error-handler/SKILL.md

Last Verified

January 24, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/JuniYadi/claude-code/blob/main/issue-reviews/skills/error-handler/SKILL.md -a claude-code --skill error-handler

Installation paths:

Claude
.claude/skills/error-handler/
Powered by add-skill CLI

Instructions

## Purpose

Handle failures gracefully:
- Post clear error messages to issues
- Provide troubleshooting steps
- Preserve partial progress
- Never fail silently

## Usage

Include this file when handling errors:

```
Use lib/error-handler to handle [error type] gracefully
```

## Error Response Templates

### 1. Issue Validation Failed

**When:** Issue missing trigger label, closed, or not found

**Template:**
\`\`\`markdown
โš ๏ธ **Cannot Process Issue**

This issue needs the \`claude:auto-fix\` label to be processed automatically.

**To enable automatic handling:**
\`\`\`bash
gh issue edit <issue-number> --add-label "claude:auto-fix"
\`\`\`

Then run: \`/handle-issue <issue-number>\`
\`\`\`

**Post to:** Issue comment
**Exit:** Gracefully (not a failure)

### 2. Code Exploration Found Nothing

**When:** Targeted search and deep analysis return no results

**Template:**
\`\`\`markdown
๐Ÿ” **Analysis Incomplete**

I searched the codebase but couldn't confidently locate code related to this issue.

**What I searched for:**
- Keywords: \`<keyword1>\`, \`<keyword2>\`, \`<keyword3>\`
- File patterns: \`**/*<pattern>*.{ts,js}\`
- Error traces: <extracted errors>

**Possible reasons:**
- Issue description may need more technical details (file names, function names, error messages)
- Code may be in a different location than expected
- Issue may require domain knowledge I don't have

**Next steps:**
- Add more technical details to the issue description
- Mention specific files or functions involved
- Run \`/handle-issue <issue-number>\` again after updating

Alternatively, this may require manual investigation.
\`\`\`

**Post to:** Issue comment
**Exit:** Gracefully (partial success)

### 3. Approval Check Failed

**When:** Can't access GitHub API, can't parse comments

**Template:**
\`\`\`markdown
โš ๏ธ **Approval Check Failed**

I couldn't verify approval due to an error:
\`\`\`
<error message>
\`\`\`

**Manual verification:**
1. Ensure you've approved the plan (๐Ÿ‘ or 'approve' c

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
7866 chars