code-simplifier

Estrelas17

Forks2

Atualizado25 de julho de 2026 às 12:08

Use when simplifying recently touched code without changing behavior, especially when asked to "simplify code", "clean up code", "refactor for clarity", or "improve readability".

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

l-lin

l-lin/dotfiles

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	code-simplifier
description	Use when simplifying recently touched code without changing behavior, especially when asked to "simplify code", "clean up code", "refactor for clarity", or "improve readability".

Simplify recent code. Preserve behavior. Follow project standards.

Find the code the user changed, or the code touched in this session. Ignore unrelated areas unless the user asks for a broader pass.
Read the repo guidance, especially AGENTS.md when present, and match existing project conventions.
Simplify for clarity:
- remove dead helpers, duplication, and needless comments
- reduce nesting and conditional sprawl
- prefer explicit names and straightforward control flow
- avoid clever one-liners and nested ternaries
Keep the smallest safe diff. Do not add abstractions, config, or helpers unless they make the touched code easier to understand right now.
Preserve behavior exactly. If intent or safety is unclear, stop and ask instead of guessing.
Verify the result against the changed code, then report only the simplifications that matter to understanding.

Mais deste repositório

mesmo repositório

kibana-elasticsearch

l-lin/dotfiles

Use when querying Elasticsearch through the Kibana console proxy, especially for log investigations, field-based filtering, or error triage from job or application logs.

2026-07-2517

devils-advocate

l-lin/dotfiles

Use when pressure-testing a plan, architecture, code change, or AI-generated proposal before committing, especially when hidden assumptions, production risks, or failure modes may be underexplored.

2026-07-2517

crafting-skills

l-lin/dotfiles

Use when creating or updating skills in `~/.config/ai/skills`, especially when a `SKILL.md` has a weak trigger, tangled structure, poor steering, or bloated wording.

2026-07-2517

datadog-pup

l-lin/dotfiles

Use when interacting with Datadog resources using the `pup` CLI, especially for APM traces, metrics, monitors, notebooks, and synthetic tests.

2026-07-2517

ingest-url

l-lin/dotfiles

Ingest a URL into the patient account wiki. Use when the user provides a URL (Atlassian/Confluence, web articles, documentation) and wants to add it to their research wiki. Handles fetching, markdown conversion, asset extraction, and runs the full wiki ingest workflow. Triggers on "ingest <url>", "add this to the wiki", or when user shares a URL in the context of wiki research.

2026-07-2417

journal

l-lin/dotfiles

Use at session start, after context compaction, and before session end. Owns session journals in `.sandbox/journals/`: when to create one, what prior context to read, what to log, and how to leave a resumable handoff

2026-07-1117

name	code-simplifier
description	Use when simplifying recently touched code without changing behavior, especially when asked to "simplify code", "clean up code", "refactor for clarity", or "improve readability".

Simplify recent code. Preserve behavior. Follow project standards.

Find the code the user changed, or the code touched in this session. Ignore unrelated areas unless the user asks for a broader pass.
Read the repo guidance, especially AGENTS.md when present, and match existing project conventions.
Simplify for clarity:
- remove dead helpers, duplication, and needless comments
- reduce nesting and conditional sprawl
- prefer explicit names and straightforward control flow
- avoid clever one-liners and nested ternaries
Keep the smallest safe diff. Do not add abstractions, config, or helpers unless they make the touched code easier to understand right now.
Preserve behavior exactly. If intent or safety is unclear, stop and ask instead of guessing.
Verify the result against the changed code, then report only the simplifications that matter to understanding.