Menu
Checklist and guidance for ensuring a PR is complete with code, tests, and documentation
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ê.
Baseado na classificação ocupacional SOC
Add a new runtime implementation to the kdn runtime system
Guide to using the instances manager API for workspace management and project detection
Guide to understanding and working with the kdn runtime system architecture
Guide to configuring the Podman runtime including image setup, agent configuration, and containerfile generation
Conventional Commit Message Generator
Guide to the autoconf package — how secret detection, filtering, and the runner are wired together, and how to extend the system with new detector types
| name | complete-pr |
| description | Checklist and guidance for ensuring a PR is complete with code, tests, and documentation |
| argument-hint |
This skill helps ensure a pull request is complete before submission: code changes, tests covering those changes, and all relevant documentation updates.
A complete PR must include:
Work through each section below and confirm everything applies to the PR at hand.
/copyright-headers)make fmt) and passes vet (make vet)All changes need test coverage. Use /testing-commands and /testing-best-practices for patterns.
preRun / validation logicTest<Command>Cmd_Examples test validating the Example fieldt.Parallel() as its first line (unless it uses t.Setenv())t.TempDir() — never os.MkdirTemp or hardcoded pathsmake testDocumentation must stay in sync with the code. Review each area below and update what applies.
Update when the PR introduces or changes something an AI agent working in this repo needs to know:
skills/)Skills document reusable capabilities for AI agents. Update when:
skills/<name>/SKILL.md).claude/skills is already a symlink to ../.agents/skillsUpdate the README when the PR changes something a user or operator of the tool will observe:
# 1. Confirm all tests pass
make test
# 2. Confirm formatting and vet
make ci-checks
# 3. Review the diff for documentation gaps
git diff main...HEAD -- '*.go' | grep -E "^(\+func |\+type |\+const |// |//)" | head -40
# 4. Check what doc files changed alongside the code
git diff --name-only main...HEAD
Go through the checklist, open the items that apply, and complete them before marking the PR ready for review.
/commit — craft a conventional commit message for the changes/testing-commands — patterns for command unit and E2E tests/testing-best-practices — parallel execution, fakes, factory injection/copyright-headers — add or update Apache 2.0 headers/add-command-with-json — full template for a new command (includes tests and doc steps)