Clean
CheckedThis "Clean" skill removes unwanted characters and formatting from text, ensuring data consistency and improving readability for analysis.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add catlog22/claude-code-workflow --skill clean -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
catlog22
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned catlog22/claude-code-workflow at 07491b04ac.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 07491b04ac
- Manifest
- .codex/skills/clean/SKILL.md
- Scanned
- 1 file, 420 lines
About this skill
What it does
The "Clean" skill is designed to systematically remove unwanted artifacts and dead code from a project, ensuring data consistency and improving readability for analysis. It identifies stale files through mainline analysis, discovers drift from core modules, and safely removes unused sessions, documents, and dead code. The process involves analyzing git history, scanning workflows, confirming changes with user input, and then staging or permanently deleting identified items.
When to use it
- To clean up a project after a period of inactivity, removing outdated files and dependencies.
- When identifying and removing dead code that is no longer used in the codebase.
- For maintaining a consistent workflow by eliminating orphaned artifacts and documents that have drifted from the mainline.
Key capabilities
- Mainline Analysis: Identifies core modules based on commit frequency to establish a baseline for cleanup.
- Drift Discovery: Uses a subagent (
cli-explore-agent) to scan workflows and identify orphaned files or code that has deviated from the mainline. - User Confirmation: Requires user input to select categories of items to be cleaned up and to specify risk level.
- Dry Run Mode: Allows previewing cleanup actions without actually executing them (
--dry-run). - Focus Area Targeting: Enables focusing the cleanup on a specific module or path within the project using the
--focusparameter.
Example prompts
- "Clean the project with a dry run to see what would be removed."
- "Run the Clean skill, focusing on the 'utilities' directory."
- "Identify and remove drifted documents in the current project."
Tips & gotchas
- The skill requires access to git history (analyzes the last 30 days).
- It uses a subagent (
cli-explore-agent) for drift discovery, so ensure that agent is available. - User input is required during the confirmation phase to select categories and risk levels before execution.