java-dev

Standardize Java code and tests using Maven and JUnit5 guidelines.

5|Updated Mar 15, 2025
One-click install
npx skills add https://github.com/xpgcrx/dotfiles --skill java-dev-xpgcrx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-dev
Source: https://github.com/xpgcrx/dotfiles/tree/main/gemini/skills/java-dev
Command: npx skills add https://github.com/xpgcrx/dotfiles --skill java-dev-xpgcrx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Java開発の作業を標準化し、コード品質とテストの一貫性を高めるためのガイドラインです。

Core Features & Use Cases

  • テストフレームワークの方針: JUnit5 の使用を推奨します。
  • テスト作成方針: ケースが多い場合は Parameterized Test を活用します。
  • 実践的な実行手順: Maven を使ったビルドとテストの実行方法を明確にします。

Quick Start

Javaプロジェクトでこのガイドラインを参照して、MavenとJUnit5を用いたテストを実行してください。

Frequently Asked Questions about java-dev

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

FAQPage Schema
What are the guidelines for writing clean code and tests in Java?

Test design practices for Java projects recommend using JUnit5 and leveraging Parameterized Tests when handling numerous test cases to ensure consistent test coverage and maintainable code.

How do I build and run tests for a Java project using Maven and JUnit5?

To build and test a Java project, apply the standardized Maven build and test execution commands provided by the guidelines to run your JUnit5 test suites consistently.

When should I use Parameterized Tests in JUnit5?

Use Parameterized Tests in JUnit5 when you have numerous test cases to execute, allowing you to run the same test logic across multiple data sets for cleaner and more maintainable code.

Do I need Maven to apply these Java coding standards?

Yes, these Java coding standards are designed for projects using Maven, providing practical execution steps and standardized commands for building and running JUnit5 tests within that environment.

What frontmatter requirements are enforced for Java development guidelines?

The guidelines enforce mandatory frontmatter requirements for name and description fields, while supporting optional resources through scripts, references, and assets to maintain safe and standardized documentation.