Create PR and check CI status

VerifiedSafe

Creates a pull request from the current branch, links it to an issue, and monitors CI status. Removes the wip label when checks pass.

Sby Skills Guide Bot
DevelopmentBeginner
8/5/2026
Claude Code
#pull-request#github-cli#ci-status#issue-tracking#git-workflow

Recommended for

Automated summary

Creates a GitHub pull request from the current branch, links it to the issue inferred from the branch name, and then checks CI status via gh.

Strengths

  • Automatically extracts the issue number from the branch name (feature/4-xxx → 4) and adds “Closes #N” to the PR body.
  • Chains PR creation, URL display, and CI check inspection with gh pr checks.
  • Handles each outcome: removes the wip label when checks pass, re-polls when pending, and inspects logs with gh run view on failure.
  • Relies only on git and gh, with no extra dependencies.

Limitations

  • Assumes a strict branch naming convention and a base branch called main.
  • CI wait time is a fixed 20-second sleep, which may be too short or needlessly long depending on the pipeline.
  • Removing the wip label and editing issues require sufficient repository permissions.
When to use it

Use it when your branch maps to an issue and you want to open a PR and immediately learn whether CI passes.

When not to use it

Avoid it if your branches don't follow the feature/<number>-… pattern or if the PR needs a carefully hand-written description.

Security analysis

Safe
Quality score85/100

The skill only uses git and gh commands to create a pull request, check CI status, and update an issue label. No destructive commands, no network exfiltration, no obfuscation, and no handling of secrets. The operations are scoped to the current repository and are standard development workflows.

No concerns found

How this analysis is made

Examples

PR + vérification CI
現在のブランチ feature/4-ethernet-frame で /issue-pr を実行して、PR作成とCIステータス確認までやって
Open PR and wait for CI
Run /issue-pr on my current branch feature/12-add-auth — open the PR linked to issue 12 and tell me if CI passes.
CI 失敗時の調査
/issue-pr でPRを作ったけどCIがfailした。gh run view で失敗ログを確認して原因を教えて

name: issue-pr description: 現在のブランチでPull Requestを作成し、CIステータスを確認。「/issue-pr」で使用 allowed-tools: Bash(git:), Bash(gh:)

Issue PR

Instructions

  1. 現在のブランチ名を取得(git branch --show-current)
  2. ブランチ名から Issue番号を抽出(feature/4-xxx → 4)
  3. git log main..HEAD でコミット内容を確認
  4. PRタイトルとbodyを生成:
    • タイトル: コミットメッセージまたはIssueタイトルベース
    • body: Closes #<number> を含める
  5. gh pr create でPR作成
  6. PR URLを表示
  7. 少し待ってから gh pr checks <PR番号> でCIステータスを確認
  8. 全てpassしたら:
    • gh issue edit <number> --remove-label wip でwipラベルを削除
    • ユーザーに報告
  9. pendingなら待って再確認
  10. failなら原因を調査

CI確認の流れ

# PR作成後、CIが開始されるまで少し待つ
sleep 20

# ステータス確認
gh pr checks <PR番号>
  • pass: wipラベル削除、マージ可能
  • pending: しばらく待って再確認
  • fail: gh run view <run_id> --log-failed で原因調査、修正してpush

Example

ブランチ feature/4-ethernet-frame で実行:

/issue-pr

実行結果:

  • Issue #4 にリンクしたPRを作成
  • Closes #4 がbodyに含まれる
  • PR URLを表示
  • CIステータスを確認
  • 全てpass: wipラベル削除、マージ準備完了を報告

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/create-pr-and-check-ci-status-msfn18so/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/create-pr-and-check-ci-status-msfn18so' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-pr-and-check-ci-status-msfn18so/download' --output '.skill-downloads/create-pr-and-check-ci-status-msfn18so/SKILL.md.part' && mv '.skill-downloads/create-pr-and-check-ci-status-msfn18so/SKILL.md.part' '.skill-downloads/create-pr-and-check-ci-status-msfn18so/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(git:*), Bash(gh:*)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/create-pr-and-check-ci-status-msfn18so/SKILL.md' && test -s '.skill-downloads/create-pr-and-check-ci-status-msfn18so/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/issue-pr' && cp -R '.skill-downloads/create-pr-and-check-ci-status-msfn18so' '.claude/skills/issue-pr'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/create-pr-and-check-ci-status-msfn18so'

openskills read 'create-pr-and-check-ci-status-msfn18so'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/create-pr-and-check-ci-status-msfn18so/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills