AGENT SKILL

ci-fix

Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis.

License 许可
MIT
所属仓库
agisota/old-one
最近更新
2026-07-04
Stars
★ 3
Forks
1

01 前言 Front Matter

name
ci-fix
license
MIT
description
Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis.

03 SKILL.md 正文

CI Fix

Diagnose CI failures and implement fixes with minimal, targeted diffs. Pushes fixes to a dedicated branch without creating PRs.

Prerequisites

Verify GitHub CLI authentication before proceeding:

gh auth status

If not authenticated, instruct the user to run gh auth login first.

Workflow

1. Locate the Failing Run

Determine the failing workflow run. If working on a PR branch:

gh pr view --json statusCheckRollup --jq '.statusCheckRollup[] | select(.conclusion == "FAILURE")'

If working from a branch or run ID:

gh run list --branch <branch> --status failure --limit 5
gh run view <run-id> --verbose

2. Extract Failure Logs

Pull logs from failed steps to identify the root cause:

gh run view <run-id> --log-failed

For deeper inspection:

gh run view <run-id> --log --job <job-id>
gh run download <run-id> -D .artifacts/<run-id>

3. Identify Root Cause

Analyze logs for common failure patterns:

  • Build/compilation errors: Missing dependencies, type errors, syntax issues
  • Test failures: Assertion failures, timeouts, flaky tests
  • Linting/formatting: Style violations, unused imports
  • Environment issues: Missing secrets, permissions, resource limits

Prefer the smallest fix that resolves the issue. Deterministic code fixes are better than workflow plumbing changes.

4. Implement the Fix

Make minimal, scoped changes matching the repository's existing style:

  • Fix only what's broken—avoid unrelated refactoring
  • Keep changes to the failing job/step when possible
  • If modifying workflow files, preserve existing permissions and avoid expanding token access

5. Push to Fix Branch

Create or update a dedicated fix branch:

git checkout -b ci-fix/<original-branch>
git add -A
git commit -m "fix: resolve CI failure in <job-name>

Co-Authored-By: Warp <agent@warp.dev>"
git push -u origin ci-fix/<original-branch>

If the fix branch already exists, update it:

git checkout ci-fix/<original-branch>
git pull origin <original-branch>
# make fixes
git commit -m "fix: <description>

Co-Authored-By: Warp <agent@warp.dev>"
git push

6. Verify the Fix

Trigger CI on the fix branch and monitor:

gh run list --branch ci-fix/<original-branch> --limit 1
gh run watch <new-run-id> --exit-status

To rerun only failed jobs:

gh run rerun <run-id> --failed

Safety Notes

  • Avoid pull_request_target unless explicitly requested—it can expose secrets to untrusted code
  • Keep workflow permissions: minimal; don't broaden access to make tests pass
  • For flaky tests, prefer deterministic fixes over blind reruns

Deliverable

After fixing, provide a brief summary:

  • Failing run: Link or ID
  • Root cause: What broke and why
  • Fix: What changed
  • Verification: New run link showing green status

04 同仓库更多 Skills

agisota
agisota/old-one

zoom-out

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

★ 3
agisota
agisota/old-one

zeroize-audit

Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.

★ 3
agisota
agisota/old-one

yeet

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

★ 3
agisota
agisota/old-one

yara-rule-authoring

Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.

★ 3
agisota
agisota/old-one

x-twitter-growth

X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.

★ 3
agisota
agisota/old-one

x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

★ 3