Run Weizhena's Deep Research workflow in Autohand Code for outline generation, deep web investigation, structured evidence capture, and final research reports.

2026-07-039

triaging-vulnerabilities-with-ssvc-framework

autohandai/community-skills

Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.

2026-07-039

aaronontheweb-dotnet-skills

autohandai/community-skills

Use Aaronontheweb dotnet-skills for Claude Code-oriented .NET maintenance, refactoring, and agent workflows.

2026-06-309

claude-skills-for-quarkus

autohandai/community-skills

Use Claude skills for Quarkus to build domain-driven Quarkus applications and Java modernization workflows.

2026-06-309

dotnet-advanced

autohandai/community-skills

Collection of .NET skills for handling specific .NET tasks for special scenarios.

2026-06-309

dotnet-ai

autohandai/community-skills

AI and ML skills for .NET: technology selection, LLM integration, agentic workflows, RAG pipelines, MCP, and classic ML with ML.NET.

2026-06-309

name	claude-code-java
description	Use claude-code-java for reusable Java project agent infrastructure, conventions, testing, and migration workflows.
license	MIT
metadata	{"author":"decebals","version":"1.0.0","source":"https://github.com/decebals/claude-code-java"}

claude-code-java

Overview

Use this skill when a Java project needs reusable coding-agent infrastructure from decebals/claude-code-java. The upstream project is optimized for Claude Code but its conventions are useful for Java agent workflows generally.

Compatibility: Java, Maven, Gradle, testing, refactoring, migration, and Claude Code-style workflows.

Workflow

Identify the Java version, build tool, framework, module layout, and test stack.
Inspect upstream instructions before importing conventions into the local repository.
Keep work tool-native: use Maven or Gradle commands already present in the project.
For migration tasks, define the source and target versions, dependency changes, and compatibility risks first.
Validate compile, tests, formatting, and static analysis according to the local project.

Guardrails

Do not mix Maven and Gradle patterns unless the repository already does.
Preserve package names, public APIs, serialization contracts, and configuration keys.
Keep framework-specific assumptions explicit, especially for Spring Boot, Quarkus, Jakarta EE, and Micronaut.
Treat generated agent instructions as project support material, not application runtime code.

Expected Output

Return Java-focused implementation or migration guidance with build commands, risk notes, and validation evidence.