Neexo Code Review Skill

A focused review skill for Neexo changes that reports real bugs, security issues, tenant isolation problems, and production risks.

CopilotCursorKilo
AuthorNeexoCore
Updated
code-reviewsecurityneexo

Install in your repo

You get: 1 SKILL.md

Copy one prompt into Cursor, Copilot, Kilo, or any agent with web access.

Install the Neexo skill "Neexo Code Review Skill" (code-review) in this repository.

Manifest: https://awesome.neexo.dk/api/install-manifest?ids=skills%2Fcode-review
Catalog: https://awesome.neexo.dk/skills/code-review

Steps:
1. Fetch https://awesome.neexo.dk/api/install-manifest?ids=skills%2Fcode-review and read the file list.
2. Fetch https://awesome.neexo.dk/api/skills/code-review/bundle and write every file to the correct project skill folder.
3. Detect IDE from this repo (.cursor → Cursor, .kilo → Kilo).
4. Preserve subdirectory structure (references/, agents/, scripts/, assets/).
5. Confirm which files you wrote.
Advanced — manual CLI
CLI — Cursor + Kilonpx awesome-neexo install skill code-review --all
CLI — Cursor onlynpx awesome-neexo install skill code-review --cursor
Copilot — full plugincopilot plugin install neexo-developer@awesome-neexo
Bundle API (JSON)https://awesome.neexo.dk/api/skills/code-review/bundle

Overview

Use this skill when reviewing a PR, staged changes, or a scoped diff. It should stay high-signal and avoid broad style feedback.

Review Priorities

  • Bugs and logic errors
  • Security vulnerabilities
  • Tenant or organization scoping mistakes
  • Data loss and migration risks
  • Missing validation or meaningful test coverage

Cost Discipline

Review selected files or diffs. Avoid scanning the whole repository unless the user explicitly asks for a repository-wide audit.

Raw content

Copy into your project — e.g. .instructions.md, .agent.md, or SKILL.md

## Overview

Use this skill when reviewing a PR, staged changes, or a scoped diff. It should stay high-signal and avoid broad style feedback.

## Review Priorities

- Bugs and logic errors
- Security vulnerabilities
- Tenant or organization scoping mistakes
- Data loss and migration risks
- Missing validation or meaningful test coverage

## Cost Discipline

Review selected files or diffs. Avoid scanning the whole repository unless the user explicitly asks for a repository-wide audit.

Next steps

Matched by shared tags and category. Browse all agents