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

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

code-review

Étoiles4

Forks3

Mis à jour8 juillet 2026 à 15:13

Review code for bugs, security issues, maintainability, tests, and project conventions. Use when the user asks for a code review or PR check.

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

akyourowngames

akyourowngames/friday

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	Review code for bugs, security issues, maintainability, tests, and project conventions. Use when the user asks for a code review or PR check.
category	coding
version	1.0.0
examples	[{"prompt":"Review this diff for bugs and missing tests."}]
test_commands	["python -m pytest tests/test_skills.py"]

Code Review

Procedure

Inspect the relevant diff and surrounding code.
Identify correctness, security, performance, maintainability, and test gaps.
Prioritize findings by impact and include file/line references when possible.
Recommend concrete fixes and verification steps.

Risk Checklist

Correctness: edge cases, invariants, error handling, concurrency, data loss.
Security: injection, path traversal, secrets, auth, unsafe command execution.
Tests: identify existing coverage, missing regression tests, and the smallest meaningful test to add.
Ownership: map each finding to the changed file/module and the nearest existing convention.
Verification: include the command or inspection that would prove the fix.

Verification

Confirm tests or checks that were run.
Do not invent behavior not visible in code or outputs.

Plus depuis ce dépôt

même dépôt

email-followup

akyourowngames/friday

Automatically notify recipients after sending emails. Use when sending emails to important contacts.

2026-07-164

goal-management

akyourowngames/friday

Capture, structure, decompose, connect, and review durable Ares goals with evidence-backed progress.

2026-07-134

goal-check-in

akyourowngames/friday

Run a concise recurring goal review from durable goal state, due dates, linked work, and progress evidence.

2026-07-134

conversation-conduct

akyourowngames/friday

Compose or reply to a chat, message, or email when the user explicitly asks to "draft a reply", "write a message", "respond to a chat", or "compose an email".

2026-07-124

browser-content-review

akyourowngames/friday

Read, extract, or summarize web-page content when the user explicitly asks to "summarize this page", "summarize the latest message", "extract the table", or "review this web content".

2026-07-124

browser-form-workflow

akyourowngames/friday

Complete a web form only when the user explicitly asks to "fill a web form", "submit a web form", "complete this form", or "enter these fields".

2026-07-124

name	code-review
description	Review code for bugs, security issues, maintainability, tests, and project conventions. Use when the user asks for a code review or PR check.
category	coding
version	1.0.0
examples	[{"prompt":"Review this diff for bugs and missing tests."}]
test_commands	["python -m pytest tests/test_skills.py"]

Code Review

Procedure

Inspect the relevant diff and surrounding code.
Identify correctness, security, performance, maintainability, and test gaps.
Prioritize findings by impact and include file/line references when possible.
Recommend concrete fixes and verification steps.

Risk Checklist

Correctness: edge cases, invariants, error handling, concurrency, data loss.
Security: injection, path traversal, secrets, auth, unsafe command execution.
Tests: identify existing coverage, missing regression tests, and the smallest meaningful test to add.
Ownership: map each finding to the changed file/module and the nearest existing convention.
Verification: include the command or inspection that would prove the fix.

Verification

Confirm tests or checks that were run.
Do not invent behavior not visible in code or outputs.