Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

opening-pr

Sterne295

Forks53

Aktualisiert7. Juli 2026 um 18:04

Implement a fix for an issue / finding / request, ensure it has a unit test or a verification path, and open the PR. Use when the user wants a change shipped as a PR — not just described, but fixed AND verified.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

SocketDev

SocketDev/socket-cli

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

consolidating-commits

SocketDev/socket-cli

Regroup the commits since the previous bump (or a given base) into logical commits — one per concern, bump kept last — via scripts/fleet/consolidate-commits.mts. "Consolidate commits" never means squash-to-one; that is squashing-history.

2026-07-09295

driving-cursor-bugbot

SocketDev/socket-cli

Drives the Cursor Bugbot review-and-fix loop on a PR. Inventories open Bugbot threads, classifies each (real bug / false positive / already fixed), fixes the real ones, replies on the inline thread (never as a detached PR comment), updates the PR title/body if scope shifted, and pushes. Use when reviewing a PR you just authored, after `gh pr create`, or after a new Bugbot pass on an existing PR.

2026-07-09295

reviewing-code

SocketDev/socket-cli

Reviews the current branch against a base ref using multiple AI backends. Runs a Workflow that streams the diff through discovery, discovery-secondary, remediation, and adversarial-verify stages, routing each stage to the available agents (codex, claude, opencode, kimi, …) and gracefully skipping any backend that isn't installed. Writes a markdown findings report under docs/. Use when preparing or updating a PR, before merging a feature branch, or when wanting an independent second opinion from a different agent.

2026-07-09295

setup-repo

SocketDev/socket-cli

Full repo onboarding wizard. Orchestrates all setup concerns for a new engineer or a fresh clone — API token, OS keychain, shell rc bridge, native messaging host, security tools, and repo-specific initialization. Invoke with /setup-repo.

2026-07-09295

cascading-fleet

SocketDev/socket-cli

Propagate a wheelhouse template change to every fleet repo. Packages the canonical fleet-repo list, the FLEET_SYNC=1 sentinel pattern, the worktree-per-repo loop, push-direct + PR-fallback, and worktree-cleanup that survives mid-loop crashes. Use when a wheelhouse template SHA needs to land in every fleet repo, or when batching multiple template SHAs into one cascade wave. Tool-version pin propagation is the wheelhouse pipeline's job (scripts/repo/pipeline.mts), not this skill's.

2026-07-09295

managing-worktrees

SocketDev/socket-cli

Manages git worktrees per the fleet's parallel-Claude-sessions rule. Creates new task-worktrees, fans out one worktree per open PR for parallel review, and prunes spent worktrees that have nothing left to land — clean trees whose branch was deleted upstream OR is fully merged into the remote default branch. Use when starting a task that needs an isolated working tree, when reviewing every open PR locally without disturbing the primary checkout, or when cleaning up after merges.

2026-07-09295

name	opening-pr
description	Implement a fix for an issue / finding / request, ensure it has a unit test or a verification path, and open the PR. Use when the user wants a change shipped as a PR — not just described, but fixed AND verified.
user-invocable	true

opening-pr

Ship a change as a PR that actually fixes the thing AND proves it — a PR without a test or a named verification path is not done. The sibling of decomposing-tickets: that one writes the work down, this one lands it.

1. Understand the target

Read the issue / finding / request and the affected code. If it's a findings report, this is the fix agent's job — deterministic fixers first, AI-patch the residue. If it's a feature or bug, drive it test-first with building-tdd.

2. Fix it

Apply the change. Deterministic fixers (pnpm run fix / format / the finding's named script) run before any hand patch (code-first-then-ai). Smallest change that resolves the target; don't refactor unrelated code.

3. Verify — the non-negotiable step

The change MUST carry one of:

A unit/integration test at the correct seam that goes red without the fix and green with it (the default — drive it via building-tdd; seam doctrine: test-layout), OR
A named verification path when a test genuinely can't reach it (a pnpm command, a check script, a reproducible manual step) — stated explicitly in the PR body, never "trust me".

Run pnpm run check + pnpm test <file> and confirm green. No green verification, no PR.

4. Write the PR body through prose + doctrine

Run the prose skill over the PR description (conversational mode) and apply prose-style-and-doctrine: lead with what changed and why, 1–3 sentences, no throat-clearers, no diff narration, evidence (the test/command that proves it). Public-surface hygiene: no real customer/company name, no private repo, no Linear ref, no bare #N (use org/repo#N or the full URL); link the issue with a closing keyword.

5. Open it

Commit on a branch (a worktree if the primary checkout has other sessions), push, gh pr create. Opening a PR is outward-facing — confirm the base branch + that the diff is the intended scope first.

Completion criterion

The fix is applied, pnpm run check + the test/verification are green, the PR body has passed the prose + doctrine pass and leaks no private name, and the PR links its issue. A PR with no test and no named verification path is not complete.