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

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

Commencer

refactor

Étoiles0

Forks0

Mis à jour13 février 2026 à 05:02

Safely refactor code while preserving test behavior

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

thirdlf03

thirdlf03/ccpeek

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

SKILL.md

readonly

name	refactor
description	Safely refactor code while preserving test behavior
allowed-tools	["Read","Write","Edit","Grep","Glob","Bash","TaskCreate","TaskUpdate","TaskList","TaskGet"]
context	fork

You are now in safe refactoring mode. Every change must keep tests green.

Instructions

Preparation
- Read the affected code and ALL related tests
- Run existing tests first:
```
pnpm vitest run
```
- They MUST pass before refactoring begins
- If tests fail, fix them first (that's a different task)
Plan
- Identify specific refactoring steps
- Create a TaskList with sequenced changes
- Each step should be ONE atomic change
Execute (for each step)
- Make ONE change (rename, extract, simplify, move)
- Run tests immediately:
```
pnpm vitest run
```
- If tests FAIL: revert the change and rethink
- If tests PASS: continue to next step

Finalize

Run full test suite:
```
pnpm vitest run
```
Run type check:
```
pnpm tsc --noEmit
```
Format:
```
pnpm biome check --write .
```

Report
- What changed and why
- Test results (before and after)
- Any risks or follow-up needed

Rules

NEVER refactor without tests passing first
ONE change at a time, tests after each
If tests break, revert IMMEDIATELY
No behavior changes during refactoring

Arguments

The user will provide the file or area to refactor and the goal.

Plus depuis ce dépôt

même dépôt

code-review

thirdlf03/ccpeek

Perform a comprehensive code quality review

2026-02-130

coding-standards

thirdlf03/ccpeek

TypeScript and Next.js coding standards. Auto-triggered when writing, reviewing, or refactoring TypeScript/React code. Covers type patterns, component patterns, Biome rules, and import conventions.

2026-02-130

frontend-patterns

thirdlf03/ccpeek

React and Next.js frontend design patterns. Auto-triggered when creating React components, implementing data fetching, managing state, or optimizing performance. Covers Server Components, Suspense, streaming, and rendering.

2026-02-130

my-plan

thirdlf03/ccpeek

Create a structured implementation plan for a feature or task

2026-02-130

notebooklm-query

thirdlf03/ccpeek

Access NotebookLM to ask questions and retrieve information. Specify a NotebookLM URL and query.

2026-02-130

resolve-reviews

thirdlf03/ccpeek

Fetch PR review comments and propose specific fixes

2026-02-130

name	refactor
description	Safely refactor code while preserving test behavior
allowed-tools	["Read","Write","Edit","Grep","Glob","Bash","TaskCreate","TaskUpdate","TaskList","TaskGet"]
context	fork

You are now in safe refactoring mode. Every change must keep tests green.

Instructions

Preparation
- Read the affected code and ALL related tests
- Run existing tests first:
```
pnpm vitest run
```
- They MUST pass before refactoring begins
- If tests fail, fix them first (that's a different task)
Plan
- Identify specific refactoring steps
- Create a TaskList with sequenced changes
- Each step should be ONE atomic change
Execute (for each step)
- Make ONE change (rename, extract, simplify, move)
- Run tests immediately:
```
pnpm vitest run
```
- If tests FAIL: revert the change and rethink
- If tests PASS: continue to next step

Finalize

Run full test suite:
```
pnpm vitest run
```
Run type check:
```
pnpm tsc --noEmit
```
Format:
```
pnpm biome check --write .
```

Report
- What changed and why
- Test results (before and after)
- Any risks or follow-up needed

Rules

NEVER refactor without tests passing first
ONE change at a time, tests after each
If tests break, revert IMMEDIATELY
No behavior changes during refactoring

Arguments

The user will provide the file or area to refactor and the goal.