pr

Estrellas0

Forks0

Actualizado10 de junio de 2026 a las 12:36

Open a pull request with a clear description, test plan, and reviewer checklist, grounded in the actual branch diff. Use when the user asks to open, create, or raise a PR.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

tenondecrpc

tenondecrpc/tenondev-agent-kit

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

Más de este repositorio

mismo repositorio

code-review

tenondecrpc/tenondev-agent-kit

Review a diff against real engineering criteria - correctness, security, tests, readability - and report findings by severity. Use when the user asks for a code review or to check a change before merge.

2026-06-100

commit

tenondecrpc/tenondev-agent-kit

Write a Conventional Commits message from the actual staged diff, then commit. Use when the user asks to commit, write a commit message, or save changes.

2026-06-100

debug

tenondecrpc/tenondev-agent-kit

Diagnose a bug systematically - reproduce, isolate, find root cause, then fix - instead of guessing at changes. Use when something is broken, failing, or behaving unexpectedly.

2026-06-100

plan

tenondecrpc/tenondev-agent-kit

Turn a vague or multi-step task into a concrete, verifiable implementation plan before writing code. Use when a task is non-trivial, ambiguous, or spans several files.

2026-06-100

name	pr
description	Open a pull request with a clear description, test plan, and reviewer checklist, grounded in the actual branch diff. Use when the user asks to open, create, or raise a PR.

pr

Open a pull request a reviewer can approve with confidence: it explains what changed and why, and shows the change was verified.

Steps

Confirm the branch state.
- Current branch and its base: git status, git branch --show-current.
- If on the default branch, stop and create a feature branch first.
- Read the full diff against the base: git diff <base>...HEAD.
- Ensure commits are pushed: git push -u origin HEAD.
Write the description from the diff, not from intentions:
- What & why: the problem and the chosen solution, in a few sentences.
- Changes: the notable changes as a short bulleted list.
- Test plan: the exact commands/steps run to verify, with their outcome.
- Risk / rollout: anything risky, breaking, or needing follow-up.
- Link issues the user references (Closes #123).
Create the PR with the gh CLI: gh pr create --title "<title>" --body "<body>" (use a heredoc for the body).
Report the PR URL.

Checklist before opening

Title follows the repo's convention (often Conventional Commits).
Tests/build pass locally; the test plan reflects what was actually run.
No secrets, debug logging, or unrelated changes in the diff.
Scope is one logical change; unrelated work is split out.

Rules

Describe only what the diff contains; do not claim tests you did not run.
Keep the description skimmable: a reviewer should grasp the change in 30 seconds.
Do not push to the default branch or force-push a shared branch.
Confirm before opening if the user has not clearly authorized creating the PR.