michael-denyer/pstack-claude

fix-ci

Find failing PR checks, inspect logs or external check links, and apply focused fixes

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/michael-denyer/pstack-claude --skill fix-ci

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Fix CI

Trigger

Branch or PR CI is failing and needs a fast, iterative path to green checks.

Workflow

  1. Resolve the active PR and inspect gh pr checks --json name,bucket,state,workflow,link.
  2. Inspect failed jobs and extract the first actionable error. Use GitHub Actions logs when available; otherwise use the check link to identify the failing command or service.
  3. Apply the smallest safe fix.
  4. Push, re-check the PR check set, and repeat until green.

Guardrails

  • Fix one actionable failure at a time.
  • Prefer minimal, low-risk changes before broader refactors.
  • Keep gh pr checks as the source of truth for overall PR CI state.

Output

  • Primary failing job and root error
  • Fixes applied in iteration order
  • Current CI status and next action

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
michael-denyer
커뮤니티

architect

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

1시간 설치 수
1
GitHub Stars
4천
업데이트
11월 4일
michael-denyer
커뮤니티

babysit

Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.

1시간 설치 수
1
GitHub Stars
4천
업데이트
11월 4일
michael-denyer
커뮤니티

benchmark-checklist

Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.

1시간 설치 수
1
GitHub Stars
4천
업데이트
11월 4일
michael-denyer
커뮤니티

blast-radius

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.

1시간 설치 수
1
GitHub Stars
4천
업데이트
11월 4일