Comments

Code comments and annotations

Showing 169-192 of 686 skills
currents-dev

playwright-best-practices

by currents-dev

Provides comprehensive guidance for writing, debugging, and maintaining Playwright tests in TypeScript. Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.

Accessibility 337 5mo ago
existential-birds

review-ai-writing

by existential-birds

Detect AI-generated writing patterns in developer text — docs, docstrings, commit messages, PR descriptions, and code comments. Use when reviewing any text artifact for authenticity and clarity.

Code Review 73 5mo ago
Dicklesworthstone

Testing Patterns

by Dicklesworthstone

Common testing patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.

Comments 182 6mo ago
jmagly

issue-auto-sync

by jmagly

MCP tools: Gitea issue management

Comments 165 6mo ago
ryoppippi

pr-apply-review

by ryoppippi

Fetch and apply review comments from the current PR. Use when you need to address PR feedback.

Code Review 246 5mo ago
kurtosis-tech

lint

by kurtosis-tech

Lint and format Kurtosis Starlark files. Check syntax, validate docstrings, and auto-format .star files. Use when writing or reviewing Starlark packages to ensure code quality.

Code Review 545 4mo ago
agentspan-ai

Agentspan — Build Durable AI Agents

by agentspan-ai

Claude Code tools are strings — ["Read", "Edit", "Bash"], not @tool functions

Comments 492 3mo ago
jaechang-hits

cellxgene-census

by jaechang-hits

"Query CELLxGENE Census (61M+ cells) programmatically. Search by cell type, tissue, disease, organism. Get expression matrices as AnnData, stream large queries out-of-core, train PyTorch models on single-cell data. For analyzing your own data use scanpy; for annotated data manipulation use anndata."

Automation 279 5mo ago
aallan

vera-language

by aallan

Write programs in the Vera programming language. Use when asked to write, edit, debug, or review Vera code (.vera files). Vera is a statically typed, purely functional language with algebraic effects, mandatory contracts, and typed slot references (@T.n) instead of variable names.

Comments 392 4d ago
Memento-Teams

docx

by Memento-Teams

"Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of \"Word doc\", \"word document\", \".docx\", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a \"report\", \"memo\", \"letter\", \"template\", or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation."

Comments 1.5K 4mo ago
curiositech

3d-cv-labeling-2026

by curiositech

Expert in 3D computer vision labeling tools, workflows, and AI-assisted annotation for LiDAR, point clouds, and sensor fusion. Covers SAM4D/Point-SAM, human-in-the-loop architectures, and vertical-specific training strategies. Activate on '3D labeling', 'point cloud annotation', 'LiDAR labeling', 'SAM 3D', 'SAM4D', 'sensor fusion annotation', '3D bounding box', 'semantic segmentation point cloud'. NOT for 2D image labeling (use clip-aware-embeddings), general ML training (use ml-engineer), video annotation without 3D (use computer-vision-pipeline), or VLM prompt engineering (use prompt-engineer).

Comments 153 6mo ago
lingzhi227

related-work-writing

by lingzhi227

Write Related Work sections that compare and contrast prior work with your approach. Organize by theme, cite broadly, and explain how your work differs. Use when writing or improving the Related Work section of a paper.

Academic 227 5mo ago
proflead

css-layout-helper

by proflead

Explain CSS layout issues and propose fixes. Use when a junior developer is struggling with alignment or spacing.

Comments 124 6mo ago
bitwarden

posting-bitwarden-review-comments

by bitwarden

Use this skill when posting inline comments to GitHub pull requests. Apply when formatting comments following Bitwarden engineering standards with severity emojis, clear explanations, and actionable suggestions. Use after findings are classified and ready to post. DO NOT USE when posting summary comments.

Code Review 128 6mo ago
bitwarden

posting-review-summary

by bitwarden

Use this skill when posting the final summary comment after all inline comments are posted. Apply as the LAST step of code review after all findings are classified and inline comments are complete. Detects context (GitHub sticky comment, new comment, or local file) and routes output accordingly.

Code Review 128 6mo ago
proflead

error-message-explainer

by proflead

Explain compiler/runtime errors in plain language. Use when a junior developer needs help understanding an error message.

Comments 124 6mo ago
CSlawyer1985

contract-review-pro

by CSlawyer1985

"专业合同审核 Skill,基于合同审核工作区成熟经验,提供7步工作流、终稿三件套、风险六维度评价"

Comments 200 2mo ago
claude-dev-suite

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

API Dev 25 5mo ago
wcygan

mysql

by wcygan

Plan and review MySQL/InnoDB schema, indexing, query tuning, transactions, and operations. Use when creating or modifying MySQL tables, indexes, or queries; diagnosing slow/locking behavior; planning migrations; or troubleshooting replication and connection issues. Load when using a MySQL database.

Comments 192 5mo ago
wcygan

context-decorate

by wcygan

Scan a codebase and place CLAUDE.md context files in directories that lack them. Spins up a team of subagents to parallelize the work — each agent covers a few directories and generates a succinct overview of the directory's purpose and key subdirectories. Use when onboarding to a new codebase, improving Claude context quality, annotating project structure, or scaffolding directory-level context for AI assistants. Keywords: context, CLAUDE.md, annotate, codebase, directory, onboard, decorate, scaffold context, context files.

Agents 192 5mo ago
wcygan

diff-explain

by wcygan

Explain a diff in plain English. Works with staged changes, unstaged changes, commits, branches, or PR numbers. Use when you want to understand what changed and why. Keywords: diff, explain diff, what changed, understand changes, diff summary, review changes, read diff

Code Review 192 5mo ago
wcygan

explain

by wcygan

Explain code, functions, modules, or programming concepts with structured walkthroughs covering purpose, patterns, data flow, edge cases, and performance. Use when explaining code, understanding how something works, learning a concept, or walking through a codebase. Keywords: explain, how does this work, what does this do, walkthrough, understand, code explanation, concept, teach, learn

Comments 192 5mo ago
NeverSight

explain

by NeverSight

"Deep explanation of complex code, files, or concepts. Routes to expert agents, uses structural search, generates mermaid diagrams. Triggers on: explain, deep dive, how does X work, architecture, data flow."

CLI Tools 185 5mo ago
sanyuan0704

code-review-expert

by sanyuan0704

"Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements."

Code Review 3.8K 4mo ago