Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

code-review

Étoiles0

Forks0

Mis à jour5 mai 2026 à 23:26

Use when reviewing code, pull requests, or diffs. Covers best practices for risk-focused review, severity ordering, and identifying missing tests or regressions.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

ivegamsft

ivegamsft/work-tracker

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	code-review
description	Use when reviewing code, pull requests, or diffs. Covers best practices for risk-focused review, severity ordering, and identifying missing tests or regressions.
compatibility	["VS Code","Cursor","Windsurf","Claude Code"]
metadata	{"category":"Uncategorized","tags":["uncategorized"],"maturity":"beta","audience":["developers"]}
allowed-tools	["bash","git","grep","find"]

Code Review

Use this skill when the task is to review code rather than write it.

Review Priorities

Bugs and behavioral regressions
Data loss, security, and correctness risks
Missing validation or broken edge cases
Missing or weak tests for changed behavior
Secondary maintainability concerns

Output Shape

Findings first, ordered by severity
File references for each finding
Open questions or assumptions
Short summary only after findings

Non-Goals

Do not rewrite the code just because there is a different style preference.
Do not bury real risks under a long summary.

Related Guardrails

Code Review Escalation — When and how to escalate findings to blocking issues vs inline comments

Plus depuis ce dépôt

même dépôt

agent-design

ivegamsft/work-tracker

Use when designing Copilot agents, authoring agent definitions, creating skill folders, or scaffolding instruction files. Provides templates and conventions for the agent ecosystem.

2026-05-050

api-design

ivegamsft/work-tracker

Use when designing, reviewing, or evolving API contracts. Provides OpenAPI templates, breaking-change checklists, versioning decision trees, and governance checklists.

2026-05-050

api-security

ivegamsft/work-tracker

API authentication, authorization, input validation, rate limiting, and protection patterns

2026-05-050

app-inventory

ivegamsft/work-tracker

Scan legacy applications to discover project structure, NuGet/npm dependencies, database connection strings, external service bindings, framework versions, and migration complexity scores. Produces structured JSON, YAML, or Markdown inventory reports.

2026-05-050

architecture

ivegamsft/work-tracker

Use when designing systems, recording architecture decisions, evaluating technologies, or assessing architectural risks. Provides C4 diagram templates, ADR format, technology selection matrices, and risk registers.

2026-05-050

azure-container-apps

ivegamsft/work-tracker

Deploy, scale, and manage containerized applications on Azure Container Apps with Dapr, revision management, and advanced networking

2026-05-050

name	code-review
description	Use when reviewing code, pull requests, or diffs. Covers best practices for risk-focused review, severity ordering, and identifying missing tests or regressions.
compatibility	["VS Code","Cursor","Windsurf","Claude Code"]
metadata	{"category":"Uncategorized","tags":["uncategorized"],"maturity":"beta","audience":["developers"]}
allowed-tools	["bash","git","grep","find"]

Code Review

Use this skill when the task is to review code rather than write it.

Review Priorities

Bugs and behavioral regressions
Data loss, security, and correctness risks
Missing validation or broken edge cases
Missing or weak tests for changed behavior
Secondary maintainability concerns

Output Shape

Findings first, ordered by severity
File references for each finding
Open questions or assumptions
Short summary only after findings

Non-Goals

Do not rewrite the code just because there is a different style preference.
Do not bury real risks under a long summary.

Related Guardrails

Code Review Escalation — When and how to escalate findings to blocking issues vs inline comments