Skill UI

This skill transforms raw API specifications, Postman collections, or verbal descriptions into clean, developer-facing documentation. It produces comprehensive guides including detailed endpoints, parameters, request/response schemas, standardized error codes, and runnable code examples, making it ideal for developer portals or README files.

This skill is designed to accurately convert complex, Hugo-managed documentation sites and content into standard Markdown format. It goes beyond generic knowledge by inspecting the entire local Hugo repository structure, including `hugo.toml`, custom shortcodes, layouts, and content files. It preserves the original content's semantic meaning while materializing Hugo-specific constructs into clean Markdown.

This skill provides an autonomous, repository-wide pipeline for auditing and fixing complex logical inconsistencies. It systematically executes stages including health checks, deep review, locating divergences, generating fixes, and performing diff-verification until the codebase is deemed clean. Ideal for maintaining high code quality and resolving deep, systemic bugs across entire projects.

Provides championship-grade repository hygiene and health checks. It systematically audits critical areas, including dependency health, CI/CD pipeline alignment, documentation synchronization, and detecting stray artifacts. The tool generates a prioritized, actionable cleanup plan and offers auto-fix capabilities to keep codebases pristine and production-ready.

A constraint-based protocol designed to professionalize existing code by normalizing comments and performing safe, non-semantic cleanup. This skill converts informal, outdated, or missing documentation into clear, concise, and professional standards without altering the core logic or behavior. Ideal for preparing code for code review, open-sourcing, or formal documentation.

A sophisticated presentation template designed for technical content, mimicking the clean, professional aesthetic of GitHub blogs or product changelogs. It features a dark GitHub-dark background, vibrant purple and blue radial ambient lighting, a multi-color gradient title, and dedicated GitHub-style code blocks. Perfect for tech talks, deep-dive tutorials, and developer documentation.

This utility provides garbage collection for Claude Code configurations. It periodically scans various directories—including skills, memory files, hooks, permissions, and caches—to identify orphaned, stale, or redundant configuration items. Crucially, the process is designed to be non-destructive, always requiring explicit human confirmation for every deletion to ensure a safe, audited cleanup process.

A comprehensive, library-agnostic checklist covering best practices for Flutter and Dart applications. It guides developers on architectural principles, state management patterns (BLoC, Riverpod, etc.), Dart idioms, performance optimization, and clean code principles, making it invaluable for code reviews.

A comprehensive guide to professional Git version control. It covers best practices for branching strategies (GitHub Flow, GitFlow, Trunk-Based), writing standardized commit messages using Conventional Commits, managing merges vs. rebases, and defining effective Pull Request workflows. Ideal for any development team looking to improve code collaboration and maintain a clean, traceable history.

A comprehensive guide detailing best practices for writing clean, maintainable, and type-safe Java code, specifically tailored for Spring Boot services. It covers naming conventions, prioritizing immutability, proper use of Optional, stream API best practices, and modern project structuring.

This skill manages the secure transition of private internal projects to public open-source releases. It executes a three-stage pipeline: Forking (removing secrets), Sanitizing (verifying clean code), and Packaging (generating required documentation like README, setup.sh, and CLAUDE.md). It ensures code safety and readiness before public deployment.

This skill automates the entire GitHub Pull Request (PR) review cycle, specifically targeting Copilot Code Review comments. It runs a robust loop: automatically triggering reviews, triaging open threads, dispatching parallel fixes that adhere to repo conventions, committing changes, and resolving comments. It continues iterating until the PR is deemed clean and ready for merge, minimizing manual effort and ensuring high code quality.