Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

leave-no-mess

Sterne89

Forks8

Aktualisiert7. Juli 2026 um 13:11

Clean up your session's side effects — background processes, temp files, debug scaffolding, test data, stashed state — before reporting done. Use at the end of any task that spawned servers, wrote scratch files, added debug output, or altered state beyond the intended diff.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

adamentwistle

adamentwistle/fable-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	leave-no-mess
description	Clean up your session's side effects — background processes, temp files, debug scaffolding, test data, stashed state — before reporting done. Use at the end of any task that spawned servers, wrote scratch files, added debug output, or altered state beyond the intended diff.

leave-no-mess

The task isn't the diff alone; it's the diff plus a workspace in the state you found it (minus the intended change).

Kill what you started: dev servers, watchers, background jobs, containers, port-holders. A zombie process from your session is the "port already in use" mystery in the user's next one. Check running background tasks before your final report.
Sweep your scaffolding out of the diff: debug prints, verbose-logging flags you flipped, hardcoded test values, commented-out experiments, TODO(remove) markers. git diff read hunk-by-hunk is the checklist (see self-review-diff) — everything there should be the change, not the process of finding it.
Scratch files go in the scratchpad, and die with the task. Throwaway repro scripts, downloaded samples, generated fixtures — if they were written into the repo, remove them or they'll show up in someone's git status as archaeology (see git-hygiene step 2).
Undo state changes made for testing: seeded rows in a shared database, modified local configs, environment variables exported for one run, git stashes you created, test users/webhooks registered against real services. External test artifacts (a queue, a webhook, a sandbox record) especially — nobody else knows they exist.
What you can't or shouldn't clean, report: a cache that will rebuild, a migration already applied, a process intentionally left serving. "Left running: dev server on :3000 for your review" converts a mess into a handoff (see honest-report).
Deliberate artifacts are not mess — the new test fixture, the added script, the updated lockfile stay. The test is intent: did the task need this to exist afterward, or did you need it to exist during?

Exit check: git status shows only intended changes; no process you spawned is still running unannounced; the next session (theirs or yours) starts clean.

Mehr aus diesem Repository

gleiches Repository

ambiguity-commit

adamentwistle/fable-skills

Resolve ambiguous requests by investigating, choosing the best-supported reading, and stating the interpretation — instead of guessing silently or blocking on questions. Use whenever a request has multiple plausible readings or an unstated parameter (which file, which env, how thorough, what format).

2026-07-0789

api-surface-care

adamentwistle/fable-skills

Treat any change to a public or shared interface — exported functions, HTTP endpoints, CLI flags, config formats, event/message schemas, DB schemas — as a contract change with consumers you can't see. Use before modifying anything other code depends on.

2026-07-0789

calibrated-recommendation

adamentwistle/fable-skills

When recommending between options, match the strength of the claim to the strength of the evidence — commit when evidence is clear, say it's a coin flip when it is. Use whenever the user asks "which should I use", "what's the best way", "A or B?", or you're proposing a design choice.

2026-07-0789

codebase-orientation

adamentwistle/fable-skills

Fast recon before changing unfamiliar code — instructions → manifest → tree → trace one flow end-to-end → git archaeology → imitate the newest precedent. Use when starting in a repo or module you haven't touched this session, or before designing against an existing architecture.

2026-07-0789

concurrency-reasoning

adamentwistle/fable-skills

Async/concurrent/streaming discipline — five questions (overlapping runs, check-then-act, mutation across await, response ordering, cancellation), idempotent retries, shared-state audit, race amplification. Use for async fan-out, streams/SSE, jobs, caches, or flaky timing-smell bugs.

2026-07-0789

context-checkpoint

adamentwistle/fable-skills

Externalize working state to files so long tasks survive context compaction and interruption. Use at the start of any task likely to exceed ~30 minutes or span many files, and again whenever a major phase completes or the plan changes.

2026-07-0789

name	leave-no-mess
description	Clean up your session's side effects — background processes, temp files, debug scaffolding, test data, stashed state — before reporting done. Use at the end of any task that spawned servers, wrote scratch files, added debug output, or altered state beyond the intended diff.

leave-no-mess

The task isn't the diff alone; it's the diff plus a workspace in the state you found it (minus the intended change).

Kill what you started: dev servers, watchers, background jobs, containers, port-holders. A zombie process from your session is the "port already in use" mystery in the user's next one. Check running background tasks before your final report.
Sweep your scaffolding out of the diff: debug prints, verbose-logging flags you flipped, hardcoded test values, commented-out experiments, TODO(remove) markers. git diff read hunk-by-hunk is the checklist (see self-review-diff) — everything there should be the change, not the process of finding it.
Scratch files go in the scratchpad, and die with the task. Throwaway repro scripts, downloaded samples, generated fixtures — if they were written into the repo, remove them or they'll show up in someone's git status as archaeology (see git-hygiene step 2).
Undo state changes made for testing: seeded rows in a shared database, modified local configs, environment variables exported for one run, git stashes you created, test users/webhooks registered against real services. External test artifacts (a queue, a webhook, a sandbox record) especially — nobody else knows they exist.
What you can't or shouldn't clean, report: a cache that will rebuild, a migration already applied, a process intentionally left serving. "Left running: dev server on :3000 for your review" converts a mess into a handoff (see honest-report).
Deliberate artifacts are not mess — the new test fixture, the added script, the updated lockfile stay. The test is intent: did the task need this to exist afterward, or did you need it to exist during?

Exit check: git status shows only intended changes; no process you spawned is still running unannounced; the next session (theirs or yours) starts clean.