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

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

implementation-review

Étoiles14

Forks2

Mis à jour6 juillet 2026 à 12:46

Implementation review, final diff review, or logic check. Use to compare code changes against the original goal, plan, and verification output.

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

Hugo-SEQUIER

Hugo-SEQUIER/my-config

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	implementation-review
description	Implementation review, final diff review, or logic check. Use to compare code changes against the original goal, plan, and verification output.

Implementation Review

Required inputs

Original request
Plan / PLAN-*.md / TASK_CONTEXT.md
Files changed
Diff summary
Commands run and output

Checklist:

Scope: only intended files changed?
Correctness: behavior matches the plan?
Logic: implementation is coherent and not accidental?
Contracts: APIs/types/config/public behavior preserved?
Regression: likely breakages?
Verification: relevant checks run and passed?

Required output template

## Verdict
- pass / pass-with-risk / fail

## Changed files reviewed
- `<path>` — <review scope>

## Blocking issues
- <issue, exact path/line if possible, why it blocks>

## Minimal required fixes
- <smallest fix that resolves the issue>

## Verification summary
- `<command>` — <result and what it proved>

## Remaining risks
- <risk or `None`>

## Confidence
- low / medium / high

Plus depuis ce dépôt

même dépôt

asset-research-skill

Hugo-SEQUIER/my-config

Use this skill when the user asks to analyze, create, or update an investment asset/company in Notion Assets / Investments. Produces professional-grade, evidence-backed asset research and then creates or updates the matching Notion asset page after confirmation.

2026-07-0614

cartography

Hugo-SEQUIER/my-config

Cartography, deep codebase map, repo map, onboarding map, or navigation index. Use for explicit codebase mapping/onboarding requests that need multiple cartography subagents and docs/indexes.

2026-07-0614

comment

Hugo-SEQUIER/my-config

Comment code, explain functions, or add documentation comments. Use to make code understandable after implementation.

2026-07-0614

commit

Hugo-SEQUIER/my-config

Commit, git commit message, or staged changes summary. Use by github agent only when the user explicitly requests a commit.

2026-07-0614

content-article

Hugo-SEQUIER/my-config

Medium article, long-form article, essay, or article from notes. Use when the user asks to create/write a Medium-style article using Content Vault evidence, positioning, and humanization rules.

2026-07-0614

content-post

Hugo-SEQUIER/my-config

LinkedIn post, social post, short content draft, or post from notes. Use when the user asks to write/create a LinkedIn/social post using the Content Vault voice, evidence, and anti-AI-writing rules.

2026-07-0614

name	implementation-review
description	Implementation review, final diff review, or logic check. Use to compare code changes against the original goal, plan, and verification output.

Implementation Review

Required inputs

Original request
Plan / PLAN-*.md / TASK_CONTEXT.md
Files changed
Diff summary
Commands run and output

Checklist:

Scope: only intended files changed?
Correctness: behavior matches the plan?
Logic: implementation is coherent and not accidental?
Contracts: APIs/types/config/public behavior preserved?
Regression: likely breakages?
Verification: relevant checks run and passed?

Required output template

## Verdict
- pass / pass-with-risk / fail

## Changed files reviewed
- `<path>` — <review scope>

## Blocking issues
- <issue, exact path/line if possible, why it blocks>

## Minimal required fixes
- <smallest fix that resolves the issue>

## Verification summary
- `<command>` — <result and what it proved>

## Remaining risks
- <risk or `None`>

## Confidence
- low / medium / high