Run any Skill in Manus with one click

commandagent-create-pr

Stars0

Forks0

UpdatedJune 18, 2026 at 06:59

Create a CommandAgent pull request from the current committed branch. Use when the user asks Codex to publish local work, open a PR, or prepare a branch for review in this repository.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Kewton

Kewton/CommandAgent

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	commandagent-create-pr
description	Create a CommandAgent pull request from the current committed branch. Use when the user asks Codex to publish local work, open a PR, or prepare a branch for review in this repository.

CommandAgent Create PR

Use this skill after the intended work is committed and verified.

Required Flow

Run git status --short --branch and inspect the branch.
Confirm the intended diff and commits belong in the PR.
Check for an existing open PR for the branch before creating a new one.
Push the current branch.
Create the PR with a body that includes summary, changed files, tests run, docs checked, risks, and follow-up.
Report the PR URL, target branch, commit range, and validation.

Target Branch Rules

Default feature/task PRs to develop.
Target main only when the user explicitly asks, or when release workflow requires it.
Do not directly push to protected or release branches when a PR is expected.
Prefer the GitHub connector for PR creation. Use gh only when authenticated and needed.

PR Body Checklist

What changed.
Why it aligns with CommandAgent's minimal design.
Public API or workflow impact.
Tests run.
Docs checked or updated.
Focused eval, if behavior changed.
Follow-up work.

More from this repository

same repository

commandagent-issue-worker

Kewton/CommandAgent

Implement one assigned CommandAgent issue or task in a dedicated git worktree. Use when Codex is working from orchestration notes, issue acceptance criteria, or a feature branch and needs a scoped implementation workflow for this repository.

2026-06-180

commandagent-orchestrate

Kewton/CommandAgent

Plan CommandAgent issue orchestration through a dry-run manifest before any worktree, CommandMate, PR, merge, or UAT action. Use when the user asks to orchestrate multiple issues or plan parallel issue work.

2026-06-180

commandagent-release-post

Kewton/CommandAgent

Draft copy-ready release announcement text for a CommandAgent release. Use when the user asks for a release post, social post, announcement, or changelog-based summary.

2026-06-180

commandagent-release

Kewton/CommandAgent

Prepare or verify a CommandAgent release using the repository release process. Use when the user asks for a release, version tag, release PR, or GitHub Release for CommandAgent.

2026-06-180

commandagent-uat

Kewton/CommandAgent

Plan and record CommandAgent UAT checks for CLI, REPL, slash-command, release, provider, or manual terminal behavior. Use when changes need user-acceptance validation beyond unit tests.

2026-06-180

commandagent-worktree-cleanup

Kewton/CommandAgent

Safely remove merged or obsolete CommandAgent git worktrees. Use when the user asks to clean up issue worktrees, feature worktrees, or all merged worktrees for this repository.

2026-06-180

name	commandagent-create-pr
description	Create a CommandAgent pull request from the current committed branch. Use when the user asks Codex to publish local work, open a PR, or prepare a branch for review in this repository.

CommandAgent Create PR

Use this skill after the intended work is committed and verified.

Required Flow

Run git status --short --branch and inspect the branch.
Confirm the intended diff and commits belong in the PR.
Check for an existing open PR for the branch before creating a new one.
Push the current branch.
Create the PR with a body that includes summary, changed files, tests run, docs checked, risks, and follow-up.
Report the PR URL, target branch, commit range, and validation.

Target Branch Rules

Default feature/task PRs to develop.
Target main only when the user explicitly asks, or when release workflow requires it.
Do not directly push to protected or release branches when a PR is expected.
Prefer the GitHub connector for PR creation. Use gh only when authenticated and needed.

PR Body Checklist

What changed.
Why it aligns with CommandAgent's minimal design.
Public API or workflow impact.
Tests run.
Docs checked or updated.
Focused eval, if behavior changed.
Follow-up work.