review-changes

Reviews Tenz project diffs across security, architecture, tests, documentation, performance, readability, and UX with severity ratings and confidence levels.

3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/tenzir/skills --skill review-changes-tenzir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-changes
Source: https://github.com/tenzir/skills/tree/main/skills/review-changes
Command: npx skills add https://github.com/tenzir/skills --skill review-changes-tenzir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured and comprehensive approach to reviewing code changes, ensuring higher quality, fewer bugs, and better maintainability.

Core Features & Use Cases

  • Systematic Code Audits: Identifies bugs, security vulnerabilities, documentation drift, and performance regressions.
  • Structured Feedback: Delivers findings with clear severity ratings, evidence, and actionable suggestions.
  • Use Case: When a pull request is submitted, use this Skill to perform a thorough code review, providing detailed feedback to the author and ensuring the changes meet project standards before merging.

Quick Start

Review the code changes in the current pull request, focusing on security and documentation.

Frequently Asked Questions about review-changes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a systematic code review for security vulnerabilities and performance regressions?

A systematic code review analyzes diffs against predefined lenses to identify security vulnerabilities, performance regressions, and architecture issues. It delivers structured feedback with severity ratings, evidence, and actionable suggestions to ensure higher code quality before merging.

What is the best way to structure pull request feedback for code quality assurance?

The best way to structure pull request feedback is to provide actionable suggestions with clear severity ratings and confidence levels. This structured feedback approach highlights critical issues across readability, documentation drift, and user experience while adhering to coding standards.

Why does documentation drift occur during code reviews and how can I identify it?

Documentation drift occurs when code changes are not reflected in updated docs. A thorough code review identifies this drift by analyzing diffs systematically, ensuring that documentation accurately reflects the current architecture and user experience standards before the changes are merged.

Does the code review process work for evaluating test coverage and readability in Tenzir projects?

Yes, the code review process evaluates test coverage and readability specifically for Tenzir projects. It analyzes changes against predefined lenses, ensuring adherence to Tenzir coding standards and review processes while providing confidence levels for each identified issue.

What are the limitations of automated code audits for finding architecture and user experience issues?

Automated code audits may struggle with subjective architecture and user experience evaluations, but this review process mitigates this by using predefined lenses and confidence levels. It focuses on objective severity ratings while still addressing complex maintainability and UX concerns.