Comments
Code comments and annotations
pr-review
by milistu
Analyze and explain a pull request to help review it effectively
conventional-comments
by milistu
Format review comments following the Conventional Comments standard. Use when writing code review comments, PR feedback, RFC reviews, peer reviews, or when the user asks for help with review comments.
slidev-drawings
by yoanbernabeu
Draw and annotate during Slidev presentations. Use this skill for live annotations, highlighting, and visual explanations.
skill-installer
by d-kimuson
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
apcball
by apcball
Review Checklist - 快速参考清单
unicode-box-drawing
by andredezzy
Unicode box drawing patterns for ASCII diagrams, flow charts, and structured text layouts in documentation and code comments.
go-api-documentation
by sentenz
Automates API documentation creation for Go projects using godoc conventions and best practices. Use when creating, modifying, or reviewing documentation comments, or when the user mentions godoc, documentation, or API docs.
Backend Engineering Skills for Doxynix
by doxynix
This philosophy guides all design decisions.
pair-mode
by ElliotJLT
When activated, Claude becomes a pair programming partner rather than a code-generation tool. Explains reasoning, teaches patterns, asks questions that build understanding, and adjusts depth based on the person's goals. Balances getting work done with building lasting knowledge. Activate with "let's pair on this" or by setting a learning focus at session start.
agentic-docs
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 like file headers, function docs, architectural decisions, or explanatory comments. Works well for both human readers and AI coding assistants who see one file at a time.
documentation-router
by Zpankz
Routes documentation and explanation tasks. Triggers on document, explain, readme, api-docs, changelog, guide, comment, describe, write-docs.
jskim
by garvit-joshi
Token-saving Java file reader. Use when working with Java files (.java) to reduce token usage. Auto-triggers when exploring, reading, or understanding Java classes, services, controllers, entities, or any .java files. Run jskim before using the Read tool on Java files to understand structure first, then Read only the lines you need.
anndata
by ovachiever
This skill should be used when working with annotated data matrices in Python, particularly for single-cell genomics analysis, managing experimental measurements with metadata, or handling large-scale biological datasets. Use when tasks involve AnnData objects, h5ad files, single-cell RNA-seq data, or integration with scanpy/scverse tools.
clinvar-database
by ovachiever
"Query NCBI ClinVar for variant clinical significance. Search by gene/position, interpret pathogenicity classifications, access via E-utilities API or FTP, annotate VCFs, for genomic medicine."
four-risks
by breethomas
Run Marty Cagan's Four Risks assessment on an issue (value, usability, feasibility, viability). Use when evaluating features before building.
postgresql
by jgamaraalv
"PostgreSQL 16+ reference for writing queries, designing schemas, managing indexes, and optimizing performance. Use when: (1) writing SQL queries (SELECT, INSERT, UPDATE, DELETE, CTEs, window functions, subqueries), (2) designing or altering table schemas (CREATE TABLE, constraints, sequences, data types), (3) choosing or creating indexes (B-tree, GIN, GiST, BRIN, partial, expression), (4) managing transactions and isolation levels (BEGIN/COMMIT, savepoints, MVCC), (5) working with JSONB data and jsonpath, (6) analyzing query performance with EXPLAIN ANALYZE, or (7) using the psql CLI."
docs_code
by vuralserhat86
Code comments, JSDoc/TSDoc ve changelog best practices.
Commenting Intent
by obra
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
Designing Before Coding
by obra
Design in pseudocode first, iterate approaches, then translate to code
Writing Evergreen Comments
by obra
Write comments explaining WHAT and WHY, never temporal context or history
fp-implement
by fiberplane
Implement work on issues. Use when user asks to "start working on issue", "what should I work on", "pick up task", "continue work", or "find next task".
moltbook
by cklxx
Interact with Moltbook (the AI agent social network) — post, browse, comment, vote, search — via shell curl.
reddit-skills
by 1146345502
Reddit automation skill collection. Supports authentication, content publishing, search & discovery, social interactions, and compound operations. Triggered when a user asks to operate Reddit (post, search, comment, login, analyze, upvote, save).
code-patterns
by xu-cell
后端代码禁令和编码规范速查。本项目是纯后端项目，前端代码在分离的项目中开发。 触发场景： - 查看项目禁止事项（后端代码） - 命名规范速查 - Git 提交规范 - 代码风格检查 - 避免过度工程 触发词：规范、禁止、命名、Git提交、代码风格、不能用、不允许、包名、架构 注意：后端 CRUD 开发规范请激活 crud-development，API 开发规范请激活 api-development，数据库设计规范请激活 database-ops。