convez.ai
SkillProdutividadeIniciante
adewale

Good PR

adewale/good-pr

Crie PRs que mantenedores querem fazer merge

Ver no GitHub
InicialPluginScore · de 0 a 100

Skill que orienta você a criar pull requests que mantenedores realmente querem fazer merge. Valida reprodução de bugs, evidências visuais, qualidade do código, testes significativos, escopo focado e descrição clara — transformando frustrações de revisores em guia prático.

Instalação

$npx convez-ai adewale/good-pr

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
5
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 2 semanas
Versão
v0.1.1
Issues abertas
6
Contribuidores
2

Casos de uso

  • Preparar pull requests para projetos open source
  • Validar qualidade e completude antes de submeter
  • Aprender padrões esperados por mantenedores

Veredito

Skill prático que resolve um problema real em open source: PRs mal estruturadas que perdem tempo de revisores. Abordagem honesta, baseada em feedback da comunidade, com checklist executável e templates úteis.

README

A tradução para o português deste README ainda está na fila.

good-pr

skills.sh

An Agent Skill that helps you craft pull requests maintainers actually want to merge.

Origin

This project was inspired by a tweet from @lukeparkerdev about the reality of community PRs in open source:

the bottom line with community PRs are they are 99% of the time slop. even in the case that it looks like a good PR, there's suspicious things. this takes the team's time. we have to exactly repro the bug (because there's no steps in the issue/PR), there's a UI change with no before/after screenshots/video, there's terrible code, there's tests that don't test anything...

Rather than complain about bad PRs, we inverted every frustration into actionable guidance. The result is a skill that walks you through exactly what maintainers wish contributors would do.

What It Does

The skill helps you prepare PRs by checking your work against the things that actually matter to reviewers:

  1. Reproduction steps — Can a maintainer reproduce the bug from your description alone?
  2. Visual evidence — Before/after screenshots or recordings for UI changes
  3. Code fit — Does your code match the project's existing patterns?
  4. Meaningful tests — Do your tests actually fail when the bug is reintroduced?
  5. Focused scope — Is the diff minimal and limited to one concern?
  6. Standalone description — Can a reviewer understand the change without pulling the code?
  7. Contributor trust — Are you building a track record, or dropping a drive-by PR?

Installation

Install with npx:

npx skills add adewale/good-pr

Skills appear on skills.sh automatically after users install the repo with the skills CLI. Install counts and leaderboard rankings come from anonymous CLI telemetry; opt out with DISABLE_TELEMETRY=1. The repo page customization in skills.sh.json is picked up after the repository is seen by telemetry and the cache refreshes.

Agent compatibility

The installable skill directory is skills/good-pr. It uses the Agent Skills SKILL.md format and is configured for Codex, OpenCode, Pi, Gemini CLI, and Claude Code.

Agent/clientInstall or use
Codexcp -R skills/good-pr ~/.codex/skills/good-pr
OpenCodecp -R skills/good-pr ~/.config/opencode/skills/good-pr or use .opencode/skills/good-pr in a project
Pipi install https://github.com/adewale/good-pr or pi --skill skills/good-pr
Gemini CLIgemini skills install https://github.com/adewale/good-pr --path skills/good-pr or copy to .gemini/skills/good-pr
Claude Codenpx skills add adewale/good-pr or copy to .claude/skills/good-pr

Or install manually by copying the skill directory:

cp -r skills/good-pr ~/.claude/skills/good-pr

You can also reference it directly in your project's .claude/settings.json.

Structure

skills/good-pr/
├── SKILL.md                      # Main skill instructions
├── references/
│   ├── pr-template.md            # Fill-in PR description template
│   └── review-checklist.md       # Self-review checklist before submitting
└── scripts/
    └── check-pr-readiness.sh     # Automated PR hygiene checks

Usage

Once installed, the skill activates when you ask your coding agent for help with pull requests:

  • "Review my PR before I submit it"
  • "Help me write a PR description for this diff"
  • "I'm contributing to an open source project, check my changes"
  • "Why do my PRs keep getting rejected?"

You can also run the readiness check script directly:

bash skills/good-pr/scripts/check-pr-readiness.sh main

Credits

  • Original insight: @lukeparkerdev — tweet
  • Skill implementation: Agent Skills-compatible instructions, tested across the shared skill eval harness

License

MIT

Ver o original no GitHub

Bom para

Relacionados