Skill

feature-submit

Creates feature branches from dev, opens GitHub draft PRs for external review by Gemini/Codex, or responds to PR feedback. Manages review cycle without self-review.

Git

Github

Gemini

git-workflow

automation

npx claudepluginhub schuettc/claude-code-plugins --plugin feature-workflow

Tool Access

This skill uses the workspace's default tool permissions.

Preview

You are executing the **SUBMIT FOR REVIEW** workflow — preparing your implementation for external review by Gemini and/or Codex reviewers via a GitHub draft PR, or responding to their PR feedback.

Supporting Assets

respond.mdsubmit.md

SKILL.md

Similar Skills

Create Pull Request

Creates and manages GitHub pull requests using GH CLI: prepares branches, reviews diffs/commits, pushes, writes titles/descriptions, requests reviewers/labels, handles feedback, merges, and cleans up. Use for feature/fix branch reviews.

agent-almanac

cm-code-review

Manages full code review lifecycle: request reviews with git SHAs after tasks, handle feedback through technical verification and response framework, complete branches after tests and linting.

pr-review

Reviews GitHub PRs: identifies feedback, selects automated-fix/merge or deliberate mode, rebases onto base branch, addresses issues, and posts comments.

1 file

claude-caliper-workflow

Stats

Parent Repo Stars11

Parent Repo Forks3

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Submit for Review

You are executing the SUBMIT FOR REVIEW workflow — preparing your implementation for external review by Gemini and/or Codex reviewers via a GitHub draft PR, or responding to their PR feedback.

Target Feature

$ARGUMENTS

Parse the arguments for:

Feature ID (required): The feature directory name

--respond flag: If present, enter respond mode to read and address PR review feedback

Mode Detection

Arguments

Mode

Skill File

<id>

Submit for review

submit.md

<id> --respond

Respond to feedback

respond.md

Step 1: Load Feature Context

Read docs/features/<id>/plan.md — confirm feature is in-progress

Read docs/features/<id>/idea.md — original problem statement

If the feature doesn't exist or has no plan.md, stop and suggest /feature-plan first.

Step 2: Route to Mode

Based on arguments, follow the appropriate mode:

No --respond flag → submit.md (create branch, open draft PR, push)

--respond flag → respond.md (read PR reviews, address feedback, push updates)

Branching Strategy

feature/<id> → dev → main

Feature branches are created from dev

Draft PRs target dev

/feature-ship merges the PR into dev

dev → main promotion is handled separately (releases, etc.)

Guidelines

Stay on the feature branch — all review work happens on feature/<id>

Commit frequently — each round of changes gets its own commit

The PR is the review artifact — all review context, feedback, and discussion lives on the PR

Validate before dismissing — if a reviewer flags something, investigate before disagreeing

Do NOT self-review — after submitting, STOP. Do not launch code review agents, run review skills, or analyze the code. External reviewers (Gemini/Codex) handle reviews in separate sessions.

No review files — do not create reviews/ directories or write review markdown files. All feedback lives on the GitHub PR.