fix-static-analysis
Skill0 starsChanged 7 months agoNo licenceView on GitHub
Investigate and resolve Java static analysis build failures by following the conventions already established in the repo. Use this skill when Maven fails due to PMD, Checkstyle, SpotBugs, FindBugs-era config, or another project static-analysis plugin and you need to decide whether to fix the code or add a narrowly scoped suppression. The skill first reads build output and project config, then checks existing exclusion and suppression patterns, then searches adjacent code for established fix-vs-suppress conventions, applies the smallest matching resolution, and verifies the result. Trigger on: "fix PMD failure", "checkstyle violation", "spotbugs error", "static analysis failed", "suppress or fix this warning", "resolve lint build failure".
In this repository27 other files it gives its agents.
- agentic-coding-auditor-skillSkill
- code-refactor-moduleSkill
- code-review-javaSkill
- code-review-skillSkill
- code-simplifySkill
- code-tdd-implSkill
- code-unit-test-implSkill
- docs-arch-summary-createSkill
- docs-impl-guide-createSkill
- docs-writing-clearly-and-conciselySkill
- feature-createSkill
- feature-implementSkill
- focus-chainSkill
- githubSkill
- imagegenSkill
- java-test-coverageSkill
- memory-bankSkill
- mvn-build-helpSkill
- openai-docsSkill
- plans-implementSkill
- plans-task-gap-plan-createSkill
- plugin-creatorSkill
- repo-onboardSkill
- skill-creatorSkill
- skill-installerSkill
- slack-messagingSkill
- test-java-onboardSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 19 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈19
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.