Skip to content
TrustedSkillsbeta
Back to all skills

Clean Code

Checked
decebals·vlatest·backend·MIT

This "Clean Code" skill automatically refactors your backend code to improve readability and maintainability, boosting developer efficiency.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add decebals/claude-code-java --skill clean-code -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

decebals

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 decebals/claude-code-java at 0d98fe9bd6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
2 files, 585 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The decebals-clean-code skill refactors Java code to improve readability and maintainability. It identifies areas of complexity, reduces redundancy, and applies coding best practices. The resulting code is cleaner, more efficient, and easier for developers to understand and modify.

When to use it

  • Refactoring legacy Java codebases to reduce technical debt.
  • Improving the clarity of complex algorithms or data structures in existing projects.
  • Preparing Java code for a new developer joining a team.
  • Automating the process of adhering to specific coding style guides within a project.

Key capabilities

  • Code refactoring
  • Readability improvement
  • Maintainability enhancement
  • Redundancy reduction
  • Coding best practices application

Example prompts

  • "Refactor this Java method to improve its readability: [paste code here]"
  • "Clean up the following class and apply standard Java coding conventions: [paste code here]"
  • “Reduce complexity in this block of code: [paste code here]”

Tips & gotchas

This skill is designed for existing Java code. It requires a codebase to operate on; it cannot generate new code from scratch. Review the refactored code carefully, as automated changes may require adjustments based on specific project context.