본문으로 건너뛰기
cccskills
무료GitHub에 공개

error-recovery-patterns

Design error recovery for gh-aw workflows, including failed installations and API calls. Define retry limits, increasing wait times, error categories, and debug logs to handle temporary failures and prevent endless retries.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Design gh-aw error handling, retry, recovery, and debugging flows.

연동 도구GitHub
설치 방법 보기

이럴 때 유용합니다

  • Add bounded retries to network operations
  • Plan recovery from installation failures
  • Handle GitHub API rate limits
  • Investigate retries using debug logs

포함된 파일(1)

  • SKILL.md3.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Error Recovery Patterns Skill

Use this skill for error handling, recovery strategies, and debugging in gh-aw.

Purpose

Implement robust recovery patterns to:

  • Reduce retry loops in agent sessions (target: <10% vs current 23%)
  • Implement circuit breakers to prevent infinite retry loops
  • Add proactive recovery for installation, dependency, and API failures
  • Improve debug logging for recovery attempts

When to Use This Skill

Use this skill when:

  • Implementing retry logic for network operations, installations, or API calls
  • Debugging retry loop issues in workflows or agent sessions
  • Adding error recovery patterns to new or existing code
  • Understanding transient vs non-transient error classification
  • Implementing circuit breakers or exponential backoff
  • Adding debug logging for recovery attempts

Key Concepts Covered

1. Circuit Breaker Pattern

  • Maximum retry limits (standard: 3 attempts)
  • Exponential backoff strategies
  • Fail-fast on non-transient errors
  • Implementation in JavaScript, Shell, and Go

2. Installation Failure Recovery

  • NPM installation with cache clearing and registry fallbacks
  • Python pip installation with mirror alternatives
  • Docker image pull with retry and rate limit handling
  • Copilot CLI installation with network retry

3. API Timeout and Rate Limit Handling

  • GitHub API rate limit detection and backoff
  • Transient error detection patterns
  • Custom retry configuration for different APIs
  • Rate limit-specific retry strategies

4. Debug Logging for Recovery

  • Logger package usage for retry attempts
  • Category naming conventions (pkg:filename)
  • DEBUG environment variable patterns
  • Zero-overhead logging when disabled

5. Error Categorization

  • Transient vs non-transient errors
  • Network errors, timeout patterns
  • HTTP error codes (502, 503, 504)
  • GitHub-specific errors (rate limits, abuse detection)

Anti-Patterns to Avoid

This skill explicitly covers anti-patterns to avoid:

  • ❌ Infinite retry loops without maximum limits
  • ❌ Retrying validation errors that won't self-correct
  • ❌ No backoff delay between attempts
  • ❌ Silent retries without logging
  • ❌ Retrying non-transient errors

Code Examples Provided

The skill includes production-ready examples for:

  • JavaScript retry with withRetry() function
  • Shell script retry loops with exponential backoff
  • Go retry patterns with context and timeouts
  • NPM/pip/docker installation recovery
  • GitHub API rate limit handling
  • Debug logging for all recovery attempts

Related Skills

  • error-messages - Error message formatting and style guide
  • error-pattern-safety - Safety guidelines for error pattern regex
  • developer - General development guidelines and conventions

Full Documentation

Complete documentation available at: ../../scratchpad/error-recovery-patterns.md

This skill references the comprehensive error recovery patterns document which includes:

  • Console formatting requirements
  • Error wrapping patterns
  • Common error scenarios with step-by-step resolution
  • Error message templates
  • Debugging runbook
  • Error categorization decision trees
  • Metrics and monitoring strategies

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Locate team files across separate working directories
  • Record decisions that affect other agents
  • Request input from another specialist
github/gh-aw5.4천2026년 10월 19일 업데이트

Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Share development rules across multiple agents
  • Keep team-specific agent names out of code and tests
  • Check affected tests before declaring work complete
github/gh-aw5.4천2026년 10월 19일 업데이트

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Designing a new workflow through questions
  • Investigating failed runs and recurring errors
  • Upgrading workflows and addressing deprecations
github/gh-aw5.4천2026년 10월 19일 업데이트

Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Proposing a major architecture change
  • Replanning milestones after a foundation change
  • Comparing technical options before seeking approval
github/gh-aw5.4천2026년 10월 19일 업데이트

Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Updating the firewall version used by gh-aw
  • Reviewing release notes for integration changes
  • Checking configuration schema differences
github/gh-aw5.4천2026년 10월 19일 업데이트

Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing git operations after repository checkout
  • Checking tokens for private cross-repository access
  • Reviewing sparse and shallow checkout changes
github/gh-aw5.4천2026년 10월 19일 업데이트

github의 스킬 모두 보기

이 스킬의 문제 신고