How do I install the Main CI Fix Pr skill?

Run npx skillmds@latest add plevasseur/main-ci-fix-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Main CI Fix Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Main CI Fix Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Main CI Fix Pr free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Main CI Fix Pr?

PLeVasseur (@plevasseur) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Main CI Fix Pr by plevasseur — Agent Skill

Name: Main CI Fix Pr
Rating: 4.2 (5 reviews)
Author: PLeVasseur

File contents

When to use

Use this skill when asked to execute a CI-fix plan as a standalone PR targeting main, especially when another feature PR already exists.

Workflow

Resolve config-plan location first:
- Run printenv OPENCODE_CONFIG_DIR.
- Read the requested plan from $OPENCODE_CONFIG_DIR/plans.
Prepare clean scope:
- Branch from main (for example fix/main-ci-failures).
- If borrowing changes from another PR for temporary validation, isolate them in a firewall branch/commit.
- Recreate the final PR branch with only intended commits.
Apply only scoped fixes from the plan.
Validate locally from repo root:
- source build/envsetup.sh highest
- cargo clippy --all-targets -- -W warnings -D warnings
- cargo test -- --test-threads 1
Flake handling:
- If publisher_subscriber misses by one message once, rerun the same serial test command once before declaring failure.
PR target safety preflight:
- Confirm branch/repo context before PR creation (git branch --show-current, git remote -v).
- Create PR with explicit target/source flags:
  - gh pr create --repo <owner>/<repo> --base main --head <fork-owner>:<branch> ...
- Verify PR routing immediately after creation:
  - gh pr view <pr-number-or-url> --repo <owner>/<repo> --json url,baseRefName,headRefName
Open PR and cross-link:
- Push branch and open PR to main.
- Comment on related PRs with the new PR URL.
- Capture the cross-link comment URL for reporting.

Scope guardrails

Keep this PR limited to CI fixes (plus feasible warning cleanup explicitly requested during validation).
Before opening PR, run:
- git log --oneline main..HEAD
- git diff --name-only main...HEAD
If output includes unrelated work, rebuild the branch with cherry-picks.

Reporting template

Always report:

Files changed
Brief diff summary
Clippy/test results (include rerun note for flaky tests)
Commit SHA(s)
PR URL
Cross-link comment URL(s)
Whether history rewrite occurred (yes/no) and final commit SHA(s)

---name: main-ci-fix-prdescription: Execute independent main-branch CI fix plans with strict scope, local validation, PR creation, and cross-linking.license: Apache-2.0---## When to useUse this skill when asked to execute a CI-fix plan as a standalone PR targeting `main`, especially when another feature PR already exists.## Workflow1. Resolve config-plan location first: - Run `printenv OPENCODE_CONFIG_DIR`. - Read the requested plan from `$OPENCODE_CONFIG_DIR/plans`.2. Prepare clean scope: - Branch from `main` (for example `fix/main-ci-failures`). - If borrowing changes from another PR for temporary validation, isolate them in a firewall branch/commit. - Recreate the final PR branch with only intended commits.3. Apply only scoped fixes from the plan.4. Validate locally from repo root: - `source build/envsetup.sh highest` - `cargo clippy --all-targets -- -W warnings -D warnings` - `cargo test -- --test-threads 1`5. Flake handling: - If `publisher_subscriber` misses by one message once, rerun the same serial test command once before declaring failure.6. PR target safety preflight: - Confirm branch/repo context before PR creation (`git branch --show-current`, `git remote -v`). - Create PR with explicit target/source flags: - `gh pr create --repo <owner>/<repo> --base main --head <fork-owner>:<branch> ...` - Verify PR routing immediately after creation: - `gh pr view <pr-number-or-url> --repo <owner>/<repo> --json url,baseRefName,headRefName`7. Open PR and cross-link: - Push branch and open PR to `main`. - Comment on related PRs with the new PR URL. - Capture the cross-link comment URL for reporting.## Scope guardrails- Keep this PR limited to CI fixes (plus feasible warning cleanup explicitly requested during validation).- Before opening PR, run: - `git log --oneline main..HEAD` - `git diff --name-only main...HEAD`- If output includes unrelated work, rebuild the branch with cherry-picks.## Reporting templateAlways report:1. Files changed2. Brief diff summary3. Clippy/test results (include rerun note for flaky tests)4. Commit SHA(s)5. PR URL6. Cross-link comment URL(s)7. Whether history rewrite occurred (yes/no) and final commit SHA(s)

Frequently asked questions

Main CI Fix Pr