How do I install the Repair Pr CI Trigger skill?

Run npx skillmds@latest add willakins/repair-pr-ci-trigger 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 Repair Pr CI Trigger safe to use?

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

Which AI agents work with Repair Pr CI Trigger?

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 Repair Pr CI Trigger free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repair Pr CI Trigger?

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

Repair Pr CI Trigger by willakins — Agent Skill

Name: Repair Pr CI Trigger
Author: willakins

Repair Pr CI Trigger

Create an empty `#CI` trigger commit on a pushed branch or PR; use only when the prompt or caller explicitly asks to trigger CI/GitHub Actions for an already-published branch. Do not use for failing CI fixes, new PRs, check monitoring, merge conflicts, dirty or divergent branches, or ordinary commit naming.

willakins dfe1180 8 files · 7.7 KB Updated Sep 17, 2026

File contents

Repair one pushed branch or PR tip by creating a marker-only commit with subject Trigger CI #CI and publishing it with a normal git push <remote> HEAD:<ref>. Use this only after explicit prompt/caller authorization to trigger CI or GitHub Actions. Use Repair Flow for exact target-resolution rules.

UTILITY SKILL. INVOKES: git, GitHub/PR metadata, enable-remote-publication. FOR SINGLE OPERATIONS: one pushed branch or PR that needs an empty CI trigger commit.

Examples

"repair PR #123 so CI runs"
"push an empty #CI commit so checks trigger"
"make GitHub Actions run for this PR head"

DO NOT USE FOR:

Fixing red GitHub Actions jobs after CI already ran.
Creating, updating, or monitoring a PR.
Choosing a normal commit subject for unpushed work.
Repairing dirty worktrees, merge conflicts, or divergent local/remote tips.

Workflow

Resolve the named PR or branch before relying on the current checkout; use the current branch only when no target was named.
Require a clean worktree and local HEAD matching the refreshed pushed tip being triggered.
Resolve the exact push destination; for open PRs, use the PR head repo/ref.
Verify shell push access before committing.
If the pushed tip message already contains #CI case-insensitively, report a no-op.
Otherwise create git commit --allow-empty -m "Trigger CI #CI" and push it to the exact resolved target.

Troubleshooting

If no matching PR-head remote or push auth exists, delegate to enable-remote-publication.
If the worktree is dirty, no remote branch exists, or local HEAD differs from the pushed tip, stop before committing.

Output

Return a short summary with branch, no-op status, previous pushed tip, trigger commit SHA when created, push status, and a labeled PR link when available.

---name: repair-pr-ci-triggerdescription: Create an empty `#CI` trigger commit on a pushed branch or PR; use only when the prompt or caller explicitly asks to trigger CI/GitHub Actions for an already-published branch. Do not use for failing CI fixes, new PRs, check monitoring, merge conflicts, dirty or divergent branches, or ordinary commit naming.---Repair one pushed branch or PR tip by creating a marker-only commit with subject `Trigger CI #CI` and publishing it with a normal `git push <remote> HEAD:<ref>`. Use this only after explicit prompt/caller authorization to trigger CI or GitHub Actions. Use [Repair Flow](references/repair-flow.md) for exact target-resolution rules.**UTILITY SKILL. INVOKES:** git, GitHub/PR metadata, `enable-remote-publication`. **FOR SINGLE OPERATIONS:** one pushed branch or PR that needs an empty CI trigger commit.## Examples- "repair PR #123 so CI runs"- "push an empty #CI commit so checks trigger"- "make GitHub Actions run for this PR head"## DO NOT USE FOR:- Fixing red GitHub Actions jobs after CI already ran.- Creating, updating, or monitoring a PR.- Choosing a normal commit subject for unpushed work.- Repairing dirty worktrees, merge conflicts, or divergent local/remote tips.## Workflow1. Resolve the named PR or branch before relying on the current checkout; use the current branch only when no target was named.2. Require a clean worktree and local `HEAD` matching the refreshed pushed tip being triggered.3. Resolve the exact push destination; for open PRs, use the PR head repo/ref.4. Verify shell push access before committing.5. If the pushed tip message already contains `#CI` case-insensitively, report a no-op.6. Otherwise create `git commit --allow-empty -m "Trigger CI #CI"` and push it to the exact resolved target.## Troubleshooting- If no matching PR-head remote or push auth exists, delegate to `enable-remote-publication`.- If the worktree is dirty, no remote branch exists, or local `HEAD` differs from the pushed tip, stop before committing.## OutputReturn a short summary with branch, no-op status, previous pushed tip, trigger commit SHA when created, push status, and a labeled PR link when available.

Frequently asked questions