Java Docs
Skill Verifiziert AktivEnsure that Java types are documented with Javadoc comments and follow best practices for documentation.
Ensure that Java code is well-documented with Javadoc comments, adhering to best practices for clarity and maintainability.
Funktionen
- Enforces Javadoc for public/protected members
- Provides guidance on documenting private members
- Details usage of Javadoc tags (@param, @return, @throws, @see, etc.)
- Explains handling of generic types and deprecation
Anwendungsfälle
- Improving code maintainability through consistent documentation
- Ensuring adherence to project-specific Javadoc standards
- Assisting developers in writing clear and effective Javadoc comments
Nicht-Ziele
- Generating Javadoc comments automatically without developer input
- Enforcing documentation for non-Java code
Installation
npx skills add github/awesome-copilotFührt das Vercel skills CLI (skills.sh) via npx aus — benötigt Node.js lokal und mindestens einen installierten skills-kompatiblen Agent (Claude Code, Cursor, Codex, …). Setzt voraus, dass das Repo dem agentskills.io-Format folgt.
Qualitätspunktzahl
VerifiziertVertrauenssignale
Ähnliche Erweiterungen
Coding Standards
100Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
Java Springboot
99Get best practices for developing applications with Spring Boot.
Neon Postgres
100Anleitungen und Best Practices für die Arbeit mit Neon Serverless Postgres. Beinhaltet den Einstieg, lokale Entwicklung mit Neon, Auswahl einer Verbindungsmethode, Neon-Funktionen, Authentifizierung (@neondatabase/auth), PostgREST-ähnliche Daten-API (@neondatabase/neon-js), Neon CLI und die Neon Platform API/SDKs. Zur Beantwortung aller Neon-bezogenen Fragen.
Sdk Dx
100Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: "SDK design", "developer experience", "API design", "SDK DX", "error messages", "type safety", "IDE integration", "SDK versioning", "migration guides", "client library design", "making SDKs feel native", "SDK best practices"
Csharp Async
100Get best practices for C# async programming
Dart Matcher Best Practices
100Best practices for using `expect` and `package:matcher`. Focuses on readable assertions, proper matcher selection, and avoiding common pitfalls.