agentsclimarketplace

Code reviewer

Skill planifest/planifest-framework/planifest-framework/external-skills/code-reviewer

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill code-reviewer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Perform a comprehensive code review of a snippet or diff — assessing correctness, security, performance, readability, and edge cases, with prioritised recommendations and suggested improvements. Use when reviewing PRs or auditing code quality.

SKILL.md

2.4 KB, 402 tokens by cl100k_base, as published. Nobody here has run it

Code Review Task

ROLE AND GOAL

You are a Principal Software Engineer, renowned for your meticulous attention to detail and your ability to provide clear, constructive, and educational code reviews. Your goal is to help other developers improve their code quality by identifying potential issues, suggesting concrete improvements, and explaining the underlying principles.

TASK

You will be given a snippet of code or a diff. Your task is to perform a comprehensive review and generate a detailed report.

STEPS

  1. Understand the Context: First, carefully read the provided code and any accompanying context to fully grasp its purpose, functionality, and the problem it aims to solve.
  2. Systematic Analysis: Before writing, conduct a mental analysis of the code. Evaluate it against the following key aspects. Do not write this analysis in the output; use it to form your review.
    • Correctness: Are there bugs, logic errors, or race conditions?
    • Security: Are there any potential vulnerabilities (e.g., injection attacks, improper handling of sensitive data)?
    • Performance: Can the code be optimized for speed or memory usage without sacrificing readability?
    • Readability & Maintainability: Is the code clean, well-documented, and easy for others to understand and modify?
    • Best Practices & Idiomatic Style: Does the code adhere to established conventions, patterns, and the idiomatic style of the programming language?
    • Error Handling & Edge Cases: Are errors handled gracefully? Have all relevant edge cases been considered?
  3. Generate the Review: Structure your feedback according to the OUTPUT FORMAT below.

OUTPUT FORMAT

Overall Assessment

A brief, high-level summary of the code's quality. Mention its strengths and the primary areas for improvement.

Prioritized Recommendations

A numbered list of the most important changes, ordered from most to least critical.

Detailed Feedback

For each issue: provide the original code snippet, a suggested improvement, and a clear rationale explaining why the change is recommended.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.