value-cleaner
/value-cleaner
Usuwa z kodu, testów, reguł i dokumentów zbędną logikę, nadmiarowe sprawdzenia, wypełniacz i treści bez wartości.
- Autor
- dabaige53 ↗
- Repozytorium
- dabaige-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 02.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 8
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 02.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/scan.py
Co robi i kiedy
Usuwa z kodu, testów, reguł i dokumentów zbędną logikę, nadmiarowe sprawdzenia, wypełniacz i treści bez wartości.
Argumenty
/value-cleaner <code|test|rule|docs> [paths]
Oryginalny opis (EN)
Use when users want to remove low-value logic, redundant checks, filler, or meaningless content from code, tests, rules, or docs.
Jak działa
- Commands
- Clean up
- Text patterns
- Judge within the asked scope
- Report
Podgląd SKILL.md
--- name: value-cleaner description: Use when users want to remove low-value logic, redundant checks, filler, or meaningless content from code, tests, rules, or docs. argument-hint: "<code|test|rule|docs> [paths]" --- # Value Cleaner Remove content that serves no actual behavior, decision, or action. Respond in the user's language. Judge every candidate with one question: > What actual behavior, decision, or action does this content serve, and is that role unique? No concrete answer: remove it. A real role already served elsewhere: keep the clearest copy. Scan hits, keywords, line counts, and file names only locate candidates; the answer decides. ## Commands The first word after the skill name selects the object; the rest are paths or instructions. Read only that object's file. | Command | Cleans | Criteria | Scan | | --- | --- | --- | --- | | `value-cleaner code` | production code | `references/code.md` | `scripts/scan.py code <paths>` | | `value-cleaner test` | tests, fixtures, snapshots, test docs | `references/test.md` | `scripts/scan.py test <paths>` | | `value-cleaner rule` | agent instructions, skill files, policies, style guides | `references/rule.md` | `scripts/scan.py rule <paths>` | | `value-cleaner docs` | READMEs, guides, plans, reports | `references/docs.md` | `scripts/scan.py docs <paths>` | Without an object, infer it from the request and paths; when the request spans several, handle one object at a time. Without paths, use the files the conversation is working on; if there are none, ask which path to clean. A command cleans by default. When the user asks only for a review, report findings as `Action | Location | Evidence`, highest value and lowest risk first, without editing. When the user asks for reusable cleanup rules, write rules instead. ## Clean up 1. Check repository status and preserve unrelated changes. 2. Run the scan on the target paths. It lists candidates as `path:line text` under each signal and never edits files. `--signal NAME` limits the output to one signal; `--root DIR` sets where references are counted, by default the repository root. 3. Read each candidate and what decides its role: callers, the boundary that validates input, rules covering the same point, the reader's task. Judge it with the object's file. Content the scan misses still counts. 4. Remove confirmed low-value content directly. Do not replace it with a new rule, a removal note, a placeholder section, or a disclaimer. Before deleting text, move any unique command, reason, or condition to its canonical location. 5. Follow the deletion granularity the user asks for. Otherwise remove the whole unit that exists only for the removed purpose (sentence, paragraph, branch, or test) instead of rewording it to do the same job. 6. Re-read the result and fix what referenced the removed content. Clean the same pattern wherever it recurs in scope. 7. Run the smallest check that covers the change with the project's own commands: affected tests, type check, or lint for code and tests; `scan.py rule` or `scan.py docs` on the edited files with `--signal broken-link --signal missing-path` for Markdown. Do not install dependencies or weaken assertions to make it pass. Once it passes, stop. ## Text patterns These recur in rules, docs, test docs, and comments. Remove the sentence or paragraph that exists only for one of them; do not substitute a softer version. - **Unrequested proof** [denial]: demands evidence for a claim nobody made. - **Stacked denials** [denial]: after a statement settles a point, another clause denies an implication nobody drew. - **Repeated checks** [duplicate]: a later sentence re-checks what an earlier one already requires. - **Empty closing summary** [closing-summary]: a final sentence restates what the content above already showed. ## Judge within the asked scope When the user asks about a dimension such as clarity, duplication, or correctness, judge that dimension and name what you checked. Do not widen the question, for example from "is this clearer" to "is this proven to convert better", and then reject the wider claim for lack of evidence. ## Report State what changed and the check result, plus blockers or failures when they exist. Use file and line references; do not list healthy items.
Pliki w paczce (8)
- SKILL.md 4 KB
- agents/openai.yaml 1 KB
- assets/icon.svg 1 KB
- references/code.md 4 KB
- references/docs.md 4 KB
- references/rule.md 3 KB
- references/test.md 18 KB
- scripts/scan.py 43 KB
Wersje
W bazie nie ma innych skilli o nazwie value-cleaner.
Migawka bazy z 13.11.2026 · wersja paczki cf36266830da (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95docs-cleaner
Konsoliduje zbędną dokumentację bez utraty wartościowej treści i utrzymuje zestaw dokumentów zgodny z prawdą po zmianach w kodzie, skryptach, konfiguracji i procedurach. - 90ai-slop-cleaner
Usuwa z kodu wygenerowanego przez AI zbędne elementy, zachowując działanie dzięki procesowi odpornemu na regresje. - 100remove-unused-includes
Znajduje i bezpiecznie usuwa nieużywane dyrektywy #include w plikach .cc projektu Brave za pomocą clang-include-cleaner, z weryfikacją budowania. - 82react-component-cleaner
Porządkuje komponent React, wyłącznie na wyraźne polecenie użytkownika. - 90deslop
Usuwa z gałęzi śmieci po kodzie generowanym przez AI: zbędne komentarze, nadmiarowe sprawdzenia, boilerplate, dryf stylu i rzutowania typów. - 90refactor-cleaner
Obsługuje zgodność wsteczną, pozwalając nowoczesnemu środowisku wykonawczemu rozpoznać starsze odwołania do capability refactor-cleaner w dawnych promptach i przepływach frameworka.