Automate a 15-point code self-review with evidence and a standardized report.
npx skills add https://github.com/s977043/plangate --skill self-review-s977043
Please help me install this Agent Skill. Skill: self-review Source: https://github.com/s977043/plangate/tree/main/.claude/skills/self-review Command: npx skills add https://github.com/s977043/plangate --skill self-review-s977043
This Skill provides a structured, repeatable self-review process to ensure changes are thoroughly evaluated before committing or opening a pull request.
Run the self-review workflow on your current branch and follow the prompts to generate a structured report.
High-intent search queries and answers about installing and using this skill.
To perform a self-review before a git commit, use a structured 15-point framework that guides you through capturing diffs, context, and rationale. This enforces evidence-based validation by requiring command outputs and tests to support all claims, preventing regressions.
Evidence-based validation for a pull request requires command outputs, test results, and rationale to support all code claims. This reduces speculative assessments and ensures changes are thoroughly evaluated, producing a documented, traceable review record for teammates.
You can generate a standardized pre-merge quality assurance report by running an automated phase-driven review workflow on your current branch. It captures diffs and context across multiple steps to create a documented, traceable record for pre-merge assurance.
Yes, the self-review workflow works for local development, pre-PR validation, and release-ready checks across team workflows. It enforces a structured 15-point self-review framework to ensure quality and traceability before committing.
The best way to enforce quality assurance before opening a pull request is applying a phase-driven review process that requires evidence from commands and tests. This creates pre-merge assurance by preventing speculative assessments and generating a traceable review record.
You need to provide command outputs and test results during code review to fulfill evidence-based validation requirements. This reduces speculative assessments by forcing developers to prove their claims, ensuring a rigorous 15-point self-review framework is met before merging.
synaptiaiRun pre-flight checks and generate a review-ready pull request body.
elijahmurrayExecute final validation checks on a pull request before merging.
nicanacReview code for correctness, security, performance, and convention compliance.
zajcaConfigure golangci-lint with recommended Go linters for static analysis.
