agentleFS
yu-iskwyu-iskw/coding-agent-fabric/.claude/skills/clean-project/SKILL.md

clean-project

Skill1 starsChanged 9 months agoApache-2.0View on GitHub

Perform a "hard reset" of the development environment. Use when dependencies are corrupted, lockfiles are out of sync, or environment tools (Trunk/pnpm) are in an inconsistent state.

  • Deletes or force-pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Remove global lockfile: rm pnpm-lock.yaml.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Clean Project (Hard Reset)

This skill provides a destructive but thorough way to repair a "broken" development environment by removing all cached artifacts and re-initializing from scratch.

When to Use

  • pnpm install fails repeatedly with checksum or resolution errors.
  • trunk reports internal errors that persist after trunk install.
  • "Ghost" errors occur (failures that don't match the current code).

Workflow

  1. Clean Dependencies:
    • Recursively delete node_modules: find . -name "node_modules" -type d -prune -exec rm -rf '{}' +.
    • Remove global lockfile: rm pnpm-lock.yaml.
  2. Clean Tooling Cache:
    • Clear Trunk cache: trunk clean.
    • Prune pnpm store: pnpm store prune.
  3. Re-initialize Environment:
    • Invoke the setup-dev-env skill to reinstall everything.
  4. Verify Health:
    • Invoke the verifier subagent (../../agents/verifier.md) to ensure the project is back to a clean, working state.

Safety Note

This process is destructive to the local environment but safe for the repository. It will require a full download of all dependencies, which may take several minutes depending on network speed.

Resources

  • pnpm Commands for Node.js: Common pnpm maintenance commands.
  • Trunk CLI Reference: Commands for managing Trunk artifacts.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.