ワンクリックでManusで任意のスキルを実行

dev-pr

スター1,547

フォーク242

更新日2026年6月27日 20:13

AI DevKit · Publish a ready feature branch for review. Use when the user wants to sync, push, and open or update a code review request on GitHub, GitLab, or another Git host.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

codeaholicguy

codeaholicguy/ai-devkit

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

ファイルエクスプローラー

2 ファイル

SKILL.md

readonly

name	dev-pr
description	AI DevKit · Publish a ready feature branch for review. Use when the user wants to sync, push, and open or update a code review request on GitHub, GitLab, or another Git host.

Dev PR

Publish an already-reviewed branch for code review. Keep this separate from commit creation: if the branch has uncommitted changes, stop and ask the user to run the commit workflow first.

Contract

Verify repository context with git status -sb, git branch --show-current, and git remote -v.
Confirm the branch is not the base branch and has committed changes to publish.
Fetch the remote before comparing or rebasing.
Rebase the feature branch onto the latest remote base branch before push/review.
Resolve conflicts carefully, preserving intended behavior, then rerun relevant validation.
Push safely. Use --force-with-lease only when a rebase rewrote an already-pushed branch.
Open or update the host's review request: PR, merge request, or equivalent.
Report review URL, branch, HEAD SHA, validation results, push mode, and risks.

Publish Workflow

Inspect local context:
- git status -sb
- git branch --show-current
- git remote -v
If uncommitted changes exist, stop. Do not stage, amend, squash, or commit in this skill.
Identify the remote and base branch from repo conventions, upstream config, or user instruction; default to origin/main only when that matches the repo.
Fetch the remote, inspect the delta, and rebase onto the remote base branch.
If conflicts occur, inspect conflicted files and git diff, resolve minimally, validate when useful, git add, then continue the rebase. Stop if the correct resolution is unclear.
Run relevant validation for the changed surface.
Push:
- First push: set upstream.
- Normal update: plain push.
- Rebased already-pushed branch: --force-with-lease.
Open or update the review request using the host's tool/API/UI (gh, glab, forge CLI, web UI, or project-specific workflow).
Write a concise review description. Include enough for reviewers to understand:
- Summary: what changed, why, and how.
- Validation: how it was verified.
- Risks: notable risks or "none known".
Report:

Review URL and state
Branch and HEAD SHA
Validation commands and exit codes
Push mode, including whether --force-with-lease was used
Risks, follow-ups, or blockers

このリポジトリの他の Skills

同じリポジトリ

dev-design

codeaholicguy/ai-devkit

AI DevKit · Design phase guidance for reviewing feature design against requirements. Use when the user wants to validate architecture, review design docs, resolve design trade-offs, or run dev-lifecycle phase 3.

2026-07-031.5k

dev-implementation

codeaholicguy/ai-devkit

AI DevKit · Implementation phase guidance for executing feature plans and checking implementation against design. Use when the user wants to implement planned tasks, update implementation docs, verify code matches design, or run dev-lifecycle phases 5 and 7.

2026-07-031.5k

dev-lifecycle

codeaholicguy/ai-devkit

AI DevKit · Orchestrator for structured SDLC phase skills. Use when the user wants to run the full lifecycle or choose the next phase across requirements, design, planning, implementation, testing, and review.

2026-07-031.5k

dev-planning

codeaholicguy/ai-devkit

AI DevKit · Planning phase guidance for creating and reconciling feature task plans. Use when the user wants to create an implementation plan, update planning docs, mark task progress, capture blockers or new tasks, or run dev-lifecycle planning work.

2026-07-031.5k

dev-requirements

codeaholicguy/ai-devkit

AI DevKit · Requirements phase guidance for starting features and reviewing requirements. Use when the user wants to capture a new requirement, clarify product scope, initialize feature docs, review requirements, or run dev-lifecycle phases 1-2.

2026-07-031.5k

dev-review

codeaholicguy/ai-devkit

AI DevKit · Final code review phase guidance for holistic pre-push review. Use when the user wants code review, final lifecycle review, design alignment checks, integration risk review, or dev-lifecycle phase 9.

2026-07-031.5k

Dev PR

Publish an already-reviewed branch for code review. Keep this separate from commit creation: if the branch has uncommitted changes, stop and ask the user to run the commit workflow first.

Contract

Verify repository context with git status -sb, git branch --show-current, and git remote -v.

Confirm the branch is not the base branch and has committed changes to publish.

Fetch the remote before comparing or rebasing.

Rebase the feature branch onto the latest remote base branch before push/review.

Resolve conflicts carefully, preserving intended behavior, then rerun relevant validation.

Push safely. Use --force-with-lease only when a rebase rewrote an already-pushed branch.

Open or update the host's review request: PR, merge request, or equivalent.

Report review URL, branch, HEAD SHA, validation results, push mode, and risks.

Publish Workflow

Inspect local context:

git status -sb
git branch --show-current
git remote -v

If uncommitted changes exist, stop. Do not stage, amend, squash, or commit in this skill.

Identify the remote and base branch from repo conventions, upstream config, or user instruction; default to origin/main only when that matches the repo.

Fetch the remote, inspect the delta, and rebase onto the remote base branch.

If conflicts occur, inspect conflicted files and git diff, resolve minimally, validate when useful, git add, then continue the rebase. Stop if the correct resolution is unclear.

Run relevant validation for the changed surface.

Push:

First push: set upstream.
Normal update: plain push.
Rebased already-pushed branch: --force-with-lease.

Open or update the review request using the host's tool/API/UI (gh, glab, forge CLI, web UI, or project-specific workflow).

Write a concise review description. Include enough for reviewers to understand:

Summary: what changed, why, and how.
Validation: how it was verified.
Risks: notable risks or "none known".

Report:

Review URL and state

Branch and HEAD SHA

Validation commands and exit codes

Push mode, including whether --force-with-lease was used

Risks, follow-ups, or blockers