Validate pull request completeness across code, tests, and documentation.
npx skills add https://github.com/openkaiden/kdn --skill complete-pr
Please help me install this Agent Skill. Skill: complete-pr Source: https://github.com/openkaiden/kdn/tree/main/.agents/skills/complete-pr Command: npx skills add https://github.com/openkaiden/kdn --skill complete-pr
PRs often lack essential elements (code, tests, and documentation), causing reviews to stall and quality to degrade. This skill provides a clear, repeatable checklist to verify that a PR is complete before submission.
Run the checklist against your current PR to confirm all required elements are included before opening the review.
High-intent search queries and answers about installing and using this skill.
To ensure pull request completeness, validate that your code, tests, and documentation are present and aligned using a checklist-driven review. This standardizes PR expectations, enforcing quality, test coverage, and documentation synchronization before opening the review.
Standardizing code review expectations across projects requires applying a repeatable checklist that verifies code, tests, and documentation synchronization. This consistency speeds up reviews, reduces back-and-forth, and helps onboard new contributors by outlining clear acceptance criteria.
PR reviews stall when essential elements like tests and documentation are missing because it degrades quality. Validating PR completeness beforehand enforces test coverage and documentation synchronization, preventing review delays and ensuring all required components are present.
Checking test coverage and documentation synchronization during a code review involves running a validation checklist against your current PR. This confirms all required elements are included, enforcing quality and ensuring docs and tests align with the requested changes before submission.
Yes, you can use checklist-driven reviews for onboarding new contributors to standard PR workflows. The checklist provides on-demand guidance that outlines acceptance criteria and documentation requirements, helping teams standardize expectations and speed up the review process.
You need to validate PR completeness for modern software projects right before opening a review. Running a checklist against your current PR confirms all required components, including code, tests, and documentation, are present and aligned to prevent quality degradation.
DethonGenerate reviewer-ready summaries of code changes with task details and changed files.
pkuppensSynchronize local Git branches and delete merged or obsolete ones.
clover-stormDetect code changes from git diffs and update corresponding documentation sections.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
