Skip to content
TrustedSkillsbeta
Back to all skills

Archunit_Import_Linter

Checked
davidcastagnetoa·vlatest·backend

This skill automatically imports ArchUnit rulesets into your project, ensuring consistent and maintainable architectural constraints.

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 davidcastagnetoa/skills --skill archunit_import_linter -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

davidcastagnetoa

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 davidcastagnetoa/skills at bd906f22af.

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

Commit
bd906f22af
Manifest
skills/archunit_import_linter/SKILL.md
Scanned
1 file, 32 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

This skill checks Java projects for correct import statements using ArchUnit's import linter. It verifies that all required imports are present and valid, helping to maintain code quality and prevent runtime errors due to missing dependencies. The skill ensures adherence to project-specific import rules and best practices.

When to use it

  • Automated Code Reviews: Integrate into CI/CD pipelines to automatically check for import issues during development.
  • Refactoring Large Projects: Quickly identify and correct incorrect or missing imports after significant code changes.
  • Onboarding New Developers: Enforce consistent import practices within a team by using the skill as part of onboarding processes.
  • Maintaining Legacy Codebases: Improve the reliability of older projects by systematically verifying import correctness.

Key capabilities

  • Java project import validation
  • ArchUnit integration
  • Automated code checking
  • Enforcement of import rules

Example prompts

  • "Check this Java project for incorrect imports."
  • "Run ArchUnit's import linter on my codebase."
  • "Verify that all required dependencies are imported correctly in src/main/java."

Tips & gotchas

  • Requires a Java development environment and ArchUnit to be installed.
  • The skill’s effectiveness depends on the accuracy of the project's configuration files.