pr

Estrelas4

Forks3

Atualizado5 de julho de 2026 às 23:39

Draft project-aligned PR descriptions from the current branch. Use when the user asks to prepare a PR description, PR notes, a branch summary for review, or to fill the repository pull request template. Follow `docs/workflows/pr-description.md` for the output shape and expectations.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

zvuk

zvuk/kithara

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	pr
description	Draft project-aligned PR descriptions from the current branch. Use when the user asks to prepare a PR description, PR notes, a branch summary for review, or to fill the repository pull request template. Follow `docs/workflows/pr-description.md` for the output shape and expectations.

PR Description

When to use

Use this skill for requests such as "prepare a PR description", "write PR notes", "summarize this branch for review", or "fill the PR template".

Workflow

Determine the base branch for the current branch comparison.
Review the branch history from the merge-base to HEAD.
Review the current diff for the same range.
If there are no committed changes in that range, inspect the current staged and unstaged changes instead and draft the PR from that evidence.
Otherwise, include staged and unstaged changes only when the user explicitly asks for them or clearly wants them included in the draft.
If you see staged or unstaged changes while preparing the draft, explicitly offer the user to commit them before finalizing the PR description.
Derive every statement from actual commits, diffs, and validation evidence.

Output rules

Write the full PR description in English, including section headings that the workflow defines (Summary, Behavior / scope, etc.), until the user requests it in another language.
Keep the description concise and reviewer-oriented.
Use the repository source structure and section names.
In Summary, explain the motivation and meaning of the change in plain reviewer-friendly language as prose, not as a checklist of bullets.
Do not invent motivation, risks, validation steps, or follow-ups; derive them from commits, diffs, and validation evidence.
If a required impact field has no evidence, write none.
If validation was not run, say so explicitly.

Repo note

In this repository, use docs/workflows/pr-description.md as the source of truth for the PR description shape.
Do not invent a parallel template when the workflow document already defines the structure.

Mais deste repositório

mesmo repositório

code-hygiene

zvuk/kithara

Validate code hygiene against kithara conventions: strict comment cleanup, ASCII/English-only sources, visibility, surface/protocol crate boundaries. Runs on the diff - aggressively flags AI-ish/redundant comments, block-label comments, status/handoff/commit markers, bloated doc comments. Triggers: clean up comments, check code hygiene, code hygiene, scrub AI code, validate comments, tidy before commit, review hygiene, check doc comments.

2026-07-054

commit

zvuk/kithara

Lint, stage, and commit changes following project conventions. Use when the user asks to commit, save changes, or says "/commit". Analyzes changes, runs linters, groups unrelated changes into separate commits, and writes conventional commit messages.

2026-07-054

name	pr
description	Draft project-aligned PR descriptions from the current branch. Use when the user asks to prepare a PR description, PR notes, a branch summary for review, or to fill the repository pull request template. Follow `docs/workflows/pr-description.md` for the output shape and expectations.

PR Description

When to use

Use this skill for requests such as "prepare a PR description", "write PR notes", "summarize this branch for review", or "fill the PR template".

Workflow

Determine the base branch for the current branch comparison.
Review the branch history from the merge-base to HEAD.
Review the current diff for the same range.
If there are no committed changes in that range, inspect the current staged and unstaged changes instead and draft the PR from that evidence.
Otherwise, include staged and unstaged changes only when the user explicitly asks for them or clearly wants them included in the draft.
If you see staged or unstaged changes while preparing the draft, explicitly offer the user to commit them before finalizing the PR description.
Derive every statement from actual commits, diffs, and validation evidence.

Output rules

Write the full PR description in English, including section headings that the workflow defines (Summary, Behavior / scope, etc.), until the user requests it in another language.
Keep the description concise and reviewer-oriented.
Use the repository source structure and section names.
In Summary, explain the motivation and meaning of the change in plain reviewer-friendly language as prose, not as a checklist of bullets.
Do not invent motivation, risks, validation steps, or follow-ups; derive them from commits, diffs, and validation evidence.
If a required impact field has no evidence, write none.
If validation was not run, say so explicitly.

Repo note

In this repository, use docs/workflows/pr-description.md as the source of truth for the PR description shape.
Do not invent a parallel template when the workflow document already defines the structure.