Refactor
CheckedAutomates Python/Node.js backend code refactoring for improved readability, performance, and maintainability using tartinerlabs' AI.
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 tartinerlabs/skills --skill refactor -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
tartinerlabs
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 tartinerlabs/skills at a7812b928c.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- a7812b928c
- Scanned
- 4 files, 341 lines
About this skill
What it does
This skill automates code refactoring for Python and Node.js backend projects, aiming to improve readability, performance, and maintainability. It leverages tartinerlabs' AI to identify and suggest fixes based on a defined set of rules categorized as General Patterns, TypeScript/JS Idioms, and Design Principles. The process involves auditing the codebase, reporting findings, and applying targeted refactorings while preserving existing behavior.
When to use it
- To improve the overall quality and maintainability of a Python or Node.js backend codebase.
- When dealing with codebases exhibiting common issues like deeply nested functions, hardcoded values, or inefficient TypeScript/JS idioms.
- As part of a regular code review process to proactively identify and address potential refactoring opportunities.
- To reduce technical debt by systematically addressing design principle violations such as tight coupling or god objects.
Key capabilities
- Code Auditing: Scans specified files, directories, or entire codebases for rule violations.
- Categorized Reporting: Groups findings into General Patterns, TypeScript/JS Idioms, and Design Principles categories.
- Targeted Refactoring: Applies minimal changes to address identified issues while preserving existing functionality.
- Rule-Based System: Operates based on a defined set of rules with detailed explanations and examples (found in the
rules/directory).
Example prompts
- "Refactor the codebase located at
/src/services." - "Audit the file
/src/api/client.tsfor TypeScript/JS idiom violations." - "Run a general refactoring audit on all files within the project."
Tips & gotchas
- The skill operates based on predefined rules; review these in the
rules/directory to understand its behavior and limitations. - Refactorings are designed to be minimal, focusing only on the identified issue. More extensive changes may require manual intervention.
- Ensure that the target scope (files or directories) is clearly defined for accurate auditing.