Automate multi-perspective code reviews from tech lead, product manager, and QA personas.
npx skills add https://github.com/gjalla/gjalla-plugin --skill perform-review
Please help me install this Agent Skill. Skill: perform-review Source: https://github.com/gjalla/gjalla-plugin/tree/main/claude/skills/perform-review Command: npx skills add https://github.com/gjalla/gjalla-plugin --skill perform-review
Three-perspective code review from Senior Tech Lead, Product Manager, and QA Engineer. Use this skill when the user wants to be sure that their feature is complete, high quality, and bug free. Triggers when the user says things like "review this code", "is this done", "is this production ready", or any request for substantive code review beyond. If the user wants both cleanup and review, use prepare-for-review first. Also triggers when you are reviewing your own implementation to ensure completeness before reporting that you're done.
Review the implementation through three expert lenses. Output is a unified checklist where each item is tagged with the persona that raised it: [TL], [PM], or [QA].
Propose a concrete, three-perspective review of the provided change by running through TL, PM, and QA checks and returning a unified checklist.
High-intent search queries and answers about installing and using this skill.
Multi-perspective code review evaluates new features by applying checks from Senior Tech Lead, Product Manager, and QA Engineer personas. It generates a unified checklist where each item is tagged by the persona that raised it.
Feature readiness verification uses a three-perspective review process to validate completeness, quality, and bug-free delivery. It loads team rules and architecture to output a tagged checklist confirming production readiness.
Reviewing your own implementation for completeness is supported by running through TL, PM, and QA checks. This ensures your code meets feature requirements and quality standards before you report being done.
To clean up code before a quality assurance review, use the prepare-for-review prompt for cleanup. Following this, the review process applies architecture and capability checks to output a unified checklist.
Multi-perspective code review applies to API changes and refactors across codebases. It validates feature readiness by loading team rules and architecture to produce a unified, persona-tagged checklist.
You need a three-perspective code review checklist when reviewing substantial code changes to ensure high quality and bug-free delivery. It applies when validating new features, API changes, or refactors across codebases.
julianjabIdentify changed files and validate them against project review rules.
KisthannyGenerate OpenSpec change proposals with proposal, design, and task artifacts.
thec3ukEnforce global tech stack standards across code files during generation, review, and refactoring.
RangeyRoverRun static analysis across multiple languages and generate prioritized issue reports.
