stack-java

Enforce Java coding style, patterns, testing conventions, and security rules before editing sources.

2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/t0lab/harness-kit --skill stack-java
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stack-java
Source: https://github.com/t0lab/harness-kit/tree/main/packages/harness-kit/skills/stack-java
Command: npx skills add https://github.com/t0lab/harness-kit --skill stack-java

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure Java code adheres to a consistent set of coding standards, patterns, testing conventions, and security rules before edits are made.

Core Features & Use Cases

  • Java coding style enforcement: loads and applies the stack-java rules from .claude/rules/stack-java/ to guide naming, layout, and types.
  • Pattern and testing guidance: provides idioms, anti-patterns, and testing framework conventions to follow.
  • Security best practices: highlights input validation and secret handling requirements to reduce vulnerabilities. Use Case: before refactoring a file, run the skill to validate conformance and surface required changes.

Quick Start

Load and apply the Java coding standards from .claude/rules/stack-java/ to the current Java file.

Frequently Asked Questions about stack-java

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Java coding standards before editing source files?

To enforce Java coding standards before edits, load the stack-java rules from the .claude/rules/stack-java/ directory to validate naming, layout, and file structure conformance during your editing workflow.

What Java security rules and testing conventions should I apply during refactoring?

Java security rules and testing conventions should cover input validation, secret handling, and framework-specific testing idioms to reduce vulnerabilities and avoid anti-patterns when refactoring source files.

Do I need specific framework dependencies to use Java coding style enforcement?

No specific framework dependencies are required for Java coding style enforcement, as the rules apply to standard Java projects across frameworks to guide file structure and naming conventions.

How do I check Java code for anti-patterns and security vulnerabilities?

To check Java code for anti-patterns and security vulnerabilities, apply rules that highlight input validation requirements, secret handling protocols, and idiomatic patterns before finalizing edits.

What is the best way to validate Java file structure and naming conventions?

The best way to validate Java file structure and naming conventions is to apply a standardized ruleset that guides type usage, layout, and naming before making source code edits.

Why does my Java project need coding style guidance before edits?

Your Java project needs coding style guidance before edits to ensure consistent adherence to patterns, testing layouts, and security rules, which reduces vulnerabilities and maintains idiomatic code.