원클릭으로 Manus에서 모든 스킬 실행

시작하기

fix-ci

스타2

포크1

업데이트2026년 6월 23일 21:19

Diagnose and fix failing CI on a PR. Capped at 3 attempts. Load repo-setup first.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

getsentry

getsentry/outpost

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Fix CI

Fix failing CI on a PR the bot authored. Load repo-setup first.

Budget

3 attempts max per PR. Count existing attempts:

ATTEMPTS=$(gh api "repos/<owner>/<repo>/issues/<number>/comments" --paginate \
  --jq '[.[] | select(.user.login == "'"$ME"'" and (.body | startswith("fix-ci: attempt")))] | length')

If >= 3, BLOCKED. Otherwise post a short comment like "fix-ci: attempt 2 — looks like a type error in foo.ts, investigating" before starting work. The fix-ci: prefix is required for counting but the rest should read naturally.

Workflow

Find failed runs: gh run list --branch <branch> --status failure
Read logs: gh run view <id> --log-failed
Categorize the failure — see references/failure-taxonomy.md for the full taxonomy and decision tree. Categories: test failure, type/lint error, build error, snapshot diff, flaky test, or infra issue.
Flaky? Re-run once (gh run rerun <id> --failed) and stop.
Infra/dependency issue? BLOCKED.
Otherwise: make the smallest fix. Reproduce locally if possible.
Load deslop and review skills.
Commit, push, and post a comment summarizing what you fixed and how. Write it like a teammate explaining the fix, not a status report.

Avoid modifying CI config unless the failure is specifically in it. Avoid bumping dependency versions — the fix should target the code, not the toolchain. Don't force-push. Don't merge.

이 저장소의 다른 Skills

같은 저장소

repo-setup

getsentry/outpost

Refresh /workspace/repo and prepare the correct branch. Load this before any situation skill.

2026-06-232

resolve-issue

getsentry/outpost

Resolve a GitHub issue end-to-end — explore, plan, implement, clean up, and open a draft PR.

2026-06-232

review-pr

getsentry/outpost

Review a pull request. Self-fix on own PRs, post a review on others'. Load repo-setup first.

2026-06-232

review

getsentry/outpost

Review the current branch's changes against intent. Returns a structured list of findings the caller can hand to a fix-applier, or an empty list when there's nothing to address. Use this for both self-review of your own work and reviewing someone else's PR.

2026-06-232

apply-fixes

getsentry/outpost

Apply review findings as the smallest code changes, then commit and push. Used on the bot's own PRs.

2026-06-232

respond-to-comment

getsentry/outpost

Triage and respond to comments on a PR. Fix if actionable, reply either way. Load repo-setup first.

2026-06-232

name	fix-ci
description	Diagnose and fix failing CI on a PR. Capped at 3 attempts. Load repo-setup first.
license	Apache-2.0
metadata	{"audience":"autonomous-agents"}

Fix CI

Fix failing CI on a PR the bot authored. Load repo-setup first.

Budget

3 attempts max per PR. Count existing attempts:

ATTEMPTS=$(gh api "repos/<owner>/<repo>/issues/<number>/comments" --paginate \
  --jq '[.[] | select(.user.login == "'"$ME"'" and (.body | startswith("fix-ci: attempt")))] | length')

Workflow

Find failed runs: gh run list --branch <branch> --status failure
Read logs: gh run view <id> --log-failed
Categorize the failure — see references/failure-taxonomy.md for the full taxonomy and decision tree. Categories: test failure, type/lint error, build error, snapshot diff, flaky test, or infra issue.
Flaky? Re-run once (gh run rerun <id> --failed) and stop.
Infra/dependency issue? BLOCKED.
Otherwise: make the smallest fix. Reproduce locally if possible.
Load deslop and review skills.
Commit, push, and post a comment summarizing what you fixed and how. Write it like a teammate explaining the fix, not a status report.

Avoid modifying CI config unless the failure is specifically in it. Avoid bumping dependency versions — the fix should target the code, not the toolchain. Don't force-push. Don't merge.