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

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

filed-code-review-to-remediation

Étoiles5

Forks1

Mis à jour23 mai 2026 à 20:23

Run or consume a workflow-driven code review and turn verified findings into a filed remediation plan. Use when the user asks for a code review report in project/research, asks to convert a review into a detailed implementation plan, or wants verified review findings prioritized before implementation.

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

Rebooted-Dev

Rebooted-Dev/Workflow-Scripts

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

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	filed-code-review-to-remediation
description	Run or consume a workflow-driven code review and turn verified findings into a filed remediation plan. Use when the user asks for a code review report in project/research, asks to convert a review into a detailed implementation plan, or wants verified review findings prioritized before implementation.

Filed Code Review To Remediation

Use this skill when review output must become a durable repo artifact and then a concrete plan.

Workflow

Read the review instructions.
- Use the exact workflow path the user named, usually under Workflow-Scripts/05-review/.
- Read the severity/priority rubric when the workflow references one.
- Honor the user's explicit output directory even if the workflow default differs.
Gather review evidence.
- Inspect current source, tests, configs, scripts, and runtime boundaries relevant to the review scope.
- Use parallel subagents for broad review areas when available, such as security, performance, correctness, and test coverage.
- Treat subagent findings as candidates until independently verified.
Verify accepted findings.
- Confirm each finding with file/line evidence, targeted repro commands, failing tests, logs, or code-path reasoning.
- Downgrade or drop speculative issues.
- Lead with bugs, risks, regressions, and missing tests.
File the review report.
- Put the report in project/research/ or the user-specified destination.
- Include severity, impact, evidence, affected files, and recommended fix direction.
- Keep summaries secondary to findings.
Create the remediation plan when asked.
- Keep planning separate from implementation until the user authorizes edits.
- Convert verified findings into phases ordered by severity, dependency, and risk.
- Include exact files, tests, verification commands, expected docs/logs, and acceptance criteria.
- Update project/plans/README.md and project/plans/TODO.md when filing an active plan.

Guardrails

Do not let workflow defaults override an explicit user filing path.
Do not patch code during a plan-only request.
Do not overstate confidence from static inspection; mark uncertain findings as follow-up research.

Plus depuis ce dépôt

même dépôt

dirty-worktree-safe-publish

Rebooted-Dev/Workflow-Scripts

Safely commit and push intended changes from a mixed or dirty worktree. Use when the user asks to push updates, commit current work, publish a fix, or handle git status with unrelated local changes, nested repositories, ignored generated files, or possible index.lock issues.

2026-05-235

execute-and-confirm-plan

Rebooted-Dev/Workflow-Scripts

Execute an approved implementation plan end to end. Use when the user says Implement the plan, points to an execute-and-confirm workflow, asks to complete a named plan, or expects code changes plus verification, changelog/troubleshooting/docs updates, and accurate plan archival or status updates.

2026-05-235

execution-artifact-triage

Rebooted-Dev/Workflow-Scripts

Triage saved runtime artifacts before editing code. Use when the user asks to inspect project/execution, project/errors, console.md, terminal.md, output.md, saved logs, warning output, large log-like files, or asks whether a warning/error needs a fix.

2026-05-235

export-render-parity-debugger

Rebooted-Dev/Workflow-Scripts

Debug and verify exported/rendered output parity across app view, HTML, Markdown, PDF, ZIP, and preview surfaces. Use when thumbnails, image links, rendered PDF, full export ZIPs, markdown previews, blog exports, or generated document styling differ from the app view or fail during export.

2026-05-235

live-bot-launch-verification

Rebooted-Dev/Workflow-Scripts

Launch or restart a local chat bot and verify real webhook health, auth, tunnel routing, and inbound/outbound delivery. Use when the user says launch my chatbot, restart after changes, verify health, run a real WhatsApp/Kapso/ngrok test, check what model/auth path is in use, or ensure home-env credentials are loaded.

2026-05-235

multi-agent-plan-orchestration

Rebooted-Dev/Workflow-Scripts

Orchestrate multiple independent agents or model passes to produce a stronger implementation plan. Use when the user asks to launch multiple agents/models, use opencode in single-line mode, run independent parallel research/proposals, add an adversarial critique stage, or synthesize a coding-agent-ready handoff plan.

2026-05-235

name	filed-code-review-to-remediation
description	Run or consume a workflow-driven code review and turn verified findings into a filed remediation plan. Use when the user asks for a code review report in project/research, asks to convert a review into a detailed implementation plan, or wants verified review findings prioritized before implementation.

Filed Code Review To Remediation

Use this skill when review output must become a durable repo artifact and then a concrete plan.

Workflow

Read the review instructions.
- Use the exact workflow path the user named, usually under Workflow-Scripts/05-review/.
- Read the severity/priority rubric when the workflow references one.
- Honor the user's explicit output directory even if the workflow default differs.
Gather review evidence.
- Inspect current source, tests, configs, scripts, and runtime boundaries relevant to the review scope.
- Use parallel subagents for broad review areas when available, such as security, performance, correctness, and test coverage.
- Treat subagent findings as candidates until independently verified.
Verify accepted findings.
- Confirm each finding with file/line evidence, targeted repro commands, failing tests, logs, or code-path reasoning.
- Downgrade or drop speculative issues.
- Lead with bugs, risks, regressions, and missing tests.
File the review report.
- Put the report in project/research/ or the user-specified destination.
- Include severity, impact, evidence, affected files, and recommended fix direction.
- Keep summaries secondary to findings.
Create the remediation plan when asked.
- Keep planning separate from implementation until the user authorizes edits.
- Convert verified findings into phases ordered by severity, dependency, and risk.
- Include exact files, tests, verification commands, expected docs/logs, and acceptance criteria.
- Update project/plans/README.md and project/plans/TODO.md when filing an active plan.

Guardrails

Do not let workflow defaults override an explicit user filing path.
Do not patch code during a plan-only request.
Do not overstate confidence from static inspection; mark uncertain findings as follow-up research.