skills.rest
aaron-vaz
aaron-vazCOMMUNITY
Explore all skills by this author →
GitHub

self-review

Analyze recent commits or branches for architectural, maintainability, performance, security, and error handling issues.

1|Updated Dec 1, 2016
Search Tags:#architecture#quality assurance#code review#feedback#development workflow#engineering
One-click install
npx skills add https://github.com/aaron-vaz/dotfiles --skill self-review-aaron-vaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: self-review
Source: https://github.com/aaron-vaz/dotfiles/tree/main/opencode/.opencode/skills/self-review
Command: npx skills add https://github.com/aaron-vaz/dotfiles --skill self-review-aaron-vaz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, staff/principal engineer-level review of your code before you submit it for team review, catching architectural issues, edge cases, and technical debt early.

Core Features & Use Cases

  • Architectural Critique: Challenges design decisions and adherence to patterns.
  • Comprehensive Analysis: Combines automated agent checks with deep manual review.
  • Direct Feedback: Delivers blunt, actionable feedback in a peer-to-peer tone.
  • Use Case: After pushing a new feature, run this skill to get a critical assessment of your code's design, maintainability, and potential failure points, ensuring higher quality before PR submission.

Quick Start

Run the self-review skill to analyze the last 5 commits on your current branch.

Frequently Asked Questions about self-review

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

FAQPage Schema
How do I get a staff engineer code review before submitting a pull request?▼

A staff engineer code review automates rigorous architectural and maintainability assessments of recent commits before team submission. It leverages specialized agents and manual oversight to deliver blunt, actionable feedback on design decisions and potential failure points.

What is the best way to check my code for architectural issues and technical debt?▼

The best way to check code for architectural issues and technical debt is to run an automated principal engineer assessment. It challenges design decisions, evaluates error handling, and identifies potential failure points to ensure higher quality.

Can I analyze an entire feature branch for maintainability and security flaws?▼

Yes, you can analyze an entire feature branch for maintainability and security flaws. The review process evaluates branches against architectural principles, performance metrics, and error handling to identify technical debt and edge cases.

Does automated code review work with my existing development workflow?▼

Automated code review integrates into your development workflow by analyzing recent commits or branches before PR submission. It requires manual oversight to simulate a principal engineer's assessment and provide direct, peer-to-peer feedback.

What are the limitations of using automated agents for code quality assurance?▼

The main limitation of automated agents for code quality assurance is that they require manual oversight to provide a fully rigorous assessment. While agents analyze performance and security, deep manual review is necessary to catch complex architectural issues.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
kyo0221kyo0221

receiving-code-review

Verify and respond to code review feedback with technical reasoning.

Community
Intermediate
crbnoscrbnos
2.3k

rust-best-practices

Guide idiomatic Rust coding practices with cargo-based feedback on code quality.

Official
Advanced
AsiaOstrichAsiaOstrich
70

discover

Assess project health, architecture, and risks in existing codebases.

Community
Intermediate