code-review

Name: code-review
Availability: InStock
Author: veilkey

Review Go and Rust code against error handling, naming, testing, and security standards.

7|3|Updated Mar 16, 2026

Search Tags:#code quality #code review #security #error handling #go #rust

Ready to run

npx skills add https://github.com/veilkey/veilkey-selfhosted --skill code-review-veilkey

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/veilkey/veilkey-selfhosted/tree/main/.dal/skills/code-review
Command: npx skills add https://github.com/veilkey/veilkey-selfhosted --skill code-review-veilkey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes skills (resource) components.

What problem does it solve?

This Skill provides comprehensive standards and practices for reviewing code in Go and Rust, ensuring code quality and consistency.

Core Features & Use Cases

Error Handling Standards: Guides on wrapping errors, avoiding ignored errors, and structured error types in Go and Rust.
Naming Conventions: Defines best practices for naming, including casing and acronym usage.
Testing Procedures: Outlines testing strategies, including success/error case coverage and testing best practices.
Code Structure & Security: Advises on function focus, length, and security considerations, including crypto and audit checks.
Use Case: A development team adopts these standards in code reviews to maintain high-quality, secure, and maintainable codebases.

Quick Start

Review existing code against these standards before merging new features or refactoring existing modules to improve quality assurance.

Frequently Asked Questions about code-review

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

FAQPage Schema

What should a code review checklist include for Go and Rust projects?▼

A code review checklist for Go and Rust should include error wrapping, naming conventions, testing coverage, and security checks. These standardized guidelines ensure consistent evaluation of error handling and code structure before merging features.

How do I standardize error handling practices in my development team?▼

To standardize error handling practices, establish guidelines for wrapping errors, avoiding ignored errors, and using structured error types. Applying these rules during code reviews maintains high-quality, secure, and maintainable codebases.

How do I review code for security vulnerabilities in Rust and Go?▼

Review code for security vulnerabilities by applying standardized checklists focusing on crypto implementation and audit checks. This process evaluates function focus and length to ensure security considerations are met during module refactoring.

Can I apply these code review guidelines to both new features and refactoring?▼

Yes, you can apply these code review guidelines to both new features and refactoring. Reviewing existing code against these standards before merges improves quality assurance and maintains consistency across development teams.

What is the best way to structure tests for Go and Rust code reviews?▼

The best way to structure tests for code reviews is to outline testing strategies that cover both success and error cases. Following these testing procedures ensures comprehensive evaluation and adherence to best practices.

Why does ignoring errors cause maintainability issues in system code?▼

Ignoring errors causes maintainability issues because it bypasses structured error types and proper error wrapping. Establishing standards to avoid ignored errors during code reviews ensures consistent high-quality software and robust error handling.