code-review

Review CampusOS code for architecture, security, quality, and documentation.

4|10|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/NITRR-Official/CampusOS --skill code-review-nitrr-official
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/NITRR-Official/CampusOS/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/NITRR-Official/CampusOS --skill code-review-nitrr-official

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that code meets high standards for architecture, security, quality, and documentation, facilitating smooth development and deployment processes in CampusOS.

Core Features & Use Cases

  • Comprehensive Code Review: Analyzes code for architecture, security, quality, and documentation.
  • Use Cases: Before submitting pull requests, during release preparation, onboarding team members, and periodic codebase audits.
  • Security Checks: Identifies hardcoded secrets, protected endpoints, and error response details.
  • Code Quality Checks: Ensures naming conventions, ES Modules, and proper error handling.
  • Documentation Review: Validates API changes, environment variables, and README commands.

Quick Start

Execute the code-review skill to perform a comprehensive code review on your pull request.

Frequently Asked Questions about code-review

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

FAQPage Schema
What does a comprehensive code review for architecture and security cover?

A comprehensive code review analyzes codebase architecture, security protocols, quality standards, and documentation completeness to ensure robust software development and deployment readiness.

How do I check my pull request for hardcoded secrets before submitting?

Run a pre-submission code review to scan for hardcoded secrets, validate protected endpoints, and verify error response details to ensure your pull request meets security protocols.

When do I need to perform a codebase audit for code quality and documentation?

Perform a codebase audit during release preparation, team onboarding, or periodic maintenance to validate API changes, verify environment variables, and ensure README commands are accurate.

Does the code review process check ES Modules and naming conventions?

Yes, the code review process verifies ES Modules usage, enforces proper naming conventions, and checks error handling to maintain strict coding quality standards.

What is the best way to validate API changes and environment variables in my code?

Use a documentation review during your code review cycle to validate API changes, check environment variables, and verify README commands for accurate technical documentation.