Skip to content
TrustedSkillsbeta
Back to all skills

Java Coding Standards

Checked
affaan-m·vlatest·backend·MIT

Enforces affaan-m's Java coding standards, ensuring consistency, readability, and maintainability across backend codebases.

Repository

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 affaan-m/ecc --skill java-coding-standards -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

affaan-m

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 affaan-m/everything-claude-code at d3b8a3e908.

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

Commit
d3b8a3e908
Manifest
skills/java-coding-standards/SKILL.md
Scanned
3 files, 836 lines
Copies in repo
3 — all of them scanned
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 Java coding standards skill ensures that Java code adheres to best practices, including proper formatting, naming conventions, and structure. It helps maintain readability, consistency, and compliance with industry guidelines such as Oracle's or Google’s Java style guides.

When to use it

  • Before committing code to a shared repository to ensure uniformity across the team.
  • During code reviews to quickly identify deviations from established standards.
  • When onboarding new developers to enforce consistent coding practices.
  • For automated CI/CD pipelines that require strict adherence to coding conventions.

Key capabilities

  • Enforces proper indentation and spacing rules.
  • Validates naming conventions for variables, methods, and classes.
  • Checks for correct use of braces and semicolons.
  • Ensures code follows documentation standards (e.g., Javadoc).
  • Supports multiple Java style guides (e.g., Oracle, Google).

Example prompts

  • "Check this Java class against the Google Java Style Guide."
  • "Format my Java method to follow Oracle's coding conventions."
  • "Identify any violations of Java naming conventions in this code snippet."

Tips & gotchas

  • Make sure your project has a defined style guide before using this skill to avoid confusion.
  • Some IDEs and linters can integrate with this skill for real-time feedback during development.