Comments
Code comments and annotations
skill-integration
by akaszubski
"Patterns for agent skill discovery, referencing, and composition using progressive disclosure architecture. Use when building agents, composing skills, or optimizing context usage. TRIGGER when: skill discovery, agent integration, skill composition, progressive disclosure. DO NOT TRIGGER when: implementing features, writing tests, documentation-only changes."
refactoring-patterns
by akaszubski
"Safe refactoring techniques — extract, inline, rename, move, simplify conditionals, and decompose functions. Use when restructuring code without changing behavior. TRIGGER when: refactor, extract method, rename, inline, simplify, decompose, clean up, code smell. DO NOT TRIGGER when: adding features, fixing bugs, writing tests, documentation."
springdoc-openapi
by claude-dev-suite
Springdoc OpenAPI for API documentation in Spring Boot. Covers Swagger UI configuration, annotations, schema customization, and security documentation. Based on production patterns from castellino and gestionale-presenze projects. USE WHEN: user mentions "Springdoc", "Spring Boot OpenAPI", "Swagger in Spring", "@Operation", "@Schema", "Swagger UI Spring", asks about "Spring Boot API documentation", "Spring REST documentation", "OpenAPI in Java" DO NOT USE FOR: General OpenAPI specs - use openapi instead; GraphQL - use graphql instead; Non-Spring Boot projects; Frontend OpenAPI generation - use openapi-codegen instead
code-review
by akaszubski
"10-point code review checklist covering correctness, tests, error handling, type hints, naming, security, and performance. Use when reviewing PRs or evaluating code quality. TRIGGER when: code review, PR review, review checklist, code quality check. DO NOT TRIGGER when: writing new code, debugging, refactoring without review context."
arkts-static-spec
by openharmonyinsight
ArkTS (Extended TypeScript) static language specification reference for OpenHarmony. Comprehensive guide covering syntax, types, classes, expressions, statements, generics, modules, annotations, and advanced features. Use when: (1) Writing or analyzing ArkTS code (.ets files), (2) Understanding ArkTS type system and type checking, (3) Implementing ArkTS language features, (4) Debugging ArkTS compilation issues, (5) Creating ArkTS developer tools or compilers, (6) Validating ArkTS code compliance, (7) Migrating from TypeScript to ArkTS. Provides detailed language rules from the official specification including lexical structure, type system, OOP features, runtime semantics, and TypeScript migration guide.
gitmoot
by gitmoot
Use Gitmoot for local-first AI agent coordination across repositories, goals, reviews, GitHub PR comments, daemon jobs, stuck jobs, branch locks, agent templates, template capture and publish/pull, custom prompt agents, orchestration, heartbeats, pipelines, memory curation, routing telemetry, event webhooks, the web dashboard, runtime metadata, and Codex, Claude Code, Kimi Code, or omp runtime workflows.
deft-directive-gh-slice
by deftai
Break a SPECIFICATION.md, PRD, or plan into independently-grabbable GitHub Issues using tracer-bullet vertical slices. Use after spec generation, when the user wants to create implementation tickets, or when breaking work into parallel-assignable issues. Requires the GitHub CLI (gh).
deft-directive-refinement
by deftai
Conversational refinement session. Ingests external work items into xBRIEF proposed/ scope, deduplicates via origin references, evaluates proposals with the user, reconciles stale origins, and promotes/demotes scopes through the lifecycle using deterministic task commands.
peat-ecosystem
by defenseunicorns
Top-level skill for Claude Code sessions across any peat-* repo. Read first, then read the per-repo SKILL.md.
deft-directive-review-cycle
by deftai
Greptile / GitHub adapter for coding/review.md: babysit a PR to merge-ready — audit process prerequisites, fetch bot findings, fix in one batch commit, exit when no P0/P1 remain. Supersedes Cursor global babysit on Deft-managed repos (#2261 / #1471).
deft-directive-article-review
by deftai
Evaluate an article, paper, or post for lessons that could improve directive. Analyzes two axes: how concepts improve directive's own implementation, and how they improve the projects directive creates. Produces filtered suggestions, iterates with the user, and optionally creates GitHub issues on the directive repo. Use when evaluating an article, paper, post, or URL for directive improvements, or when the user says "analyze this article", "evaluate this article", or "what can we learn from this for directive".
go-google-style-guide
by metalagman
Expertise in Go programming according to the Google Go Style Guide. Use when the user needs to write, refactor, or review Go code for clarity, simplicity, and maintainability. This skill ensures adherence to Google's official Go idioms, formatting, and the "Least Mechanism" principle.
dotnet-testing-autofixture-customization
by kevintsengtw
AutoFixture 進階自訂化技術完整指南。當需要自訂 AutoFixture 建構器或處理特殊型別的測試資料產生規則時使用。涵蓋 DataAnnotations 自動整合、ISpecimenBuilder 實作、優先順序管理。包含 DateTime/數值範圍建構器、泛型化設計與流暢式擴充方法。 Keywords: autofixture customization, autofixture customize, autofixture 自訂, specimen builder, ISpecimenBuilder, RandomDateTimeSequenceGenerator, NumericRangeBuilder, DataAnnotations autofixture, fixture.Customizations, Insert(0), 自訂建構器, NoSpecimen, 泛型化建構器
sqlex
by go-sqlex
sqlex is a modern enhancement wrapper for Go database/sql based on jmoiron/sqlx,
reviewdog
by AgentSecOps
Automated code review and security linting integration for CI/CD pipelines using reviewdog. Aggregates findings from multiple security and quality tools (SAST, linters, formatters) into unified code review comments on pull requests. Use when: (1) Integrating security scanning into code review workflows, (2) Automating security feedback on pull requests, (3) Consolidating multiple tool outputs into actionable review comments, (4) Enforcing secure coding standards in CI/CD pipelines, (5) Providing inline security annotations during development.
rp-mapper
by wix
Maps discovered source entities and fields to Wix targets and documents lossiness. Use when creating machine-readable mapping artifacts and review markdown after discovery.
ontology-validator
by HeshamFS
Validate material sample annotations and data structures against ontology constraints. Use when checking if CMSO annotations are correct, verifying that required properties are present, or validating that object property relationships have consistent domain and range. Catches unknown classes, unknown properties, domain mismatches, and missing required fields.
Excalidraw Generation
by rhuss
This skill should be used when the user asks to "create excalidraw diagram", "generate excalidraw", "hand-drawn diagram", "sketch diagram", "whiteboard style diagram", or when informal, spatial, annotated diagrams would best convey conceptual relationships. Expert in both presentation design AND artistic Excalidraw JSON creation.
explain
by Terryc21
'Deep-dive explanation of how a specific file, feature, or data flow works. Triggers: "explain", "how does X work", "walk me through", "what does this do".'
gsd-browser
by gsd-build
Native Rust browser automation CLI for AI agents. Use when the user needs to interact with websites — navigating pages, filling forms, clicking buttons, taking screenshots, sharing a live browser view, narrating browser actions, extracting structured data, running assertions, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "show me the browser", "share the screen", "pause the browser", "step through this", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", "visual regression test", "check for prompt injection", or any task requiring programmatic web interaction.
technical-writing
by Logos-Liber
Technical writing principles and best practices for creating clear, accurate documentation
claude-code-plugins
by melodic-software
"Verify or configure where discovery artifacts land in this repository: report the effective topic-docs concern, or persist it to the tracked .claude/topic-docs.yaml. Use when: 'set up discovery', 'configure the discovery plugin', 'is discovery configured', 'discovery setup', 'where do EXPLORE.md / RESEARCH.md land', or a discovery skill reports missing or thin config. Actions: check (read-only, default) apply (persist the concern file). Re-runnable — safe to invoke again."
code-review
by letta-ai
Skill for handling PR code reviews. Use when triggered by a PR review comment, review request, or when asked to review code changes. Provides workflow for reading review comments, understanding feedback, and iterating on changes.
code-comments
by petekp
Write clear, plain-spoken code comments and documentation that lives alongside the code. Use when writing or reviewing code that needs inline documentation—file headers, function docs, architectural decisions, or explanatory comments. Optimized for both human readers and AI coding assistants who benefit from co-located context.