Comments

Code comments and annotations

Showing 1105-1128 of 1139 skills
cuioss

ext-triage-js

by cuioss

Triage extension for JavaScript findings during plan-finalize phase

Code Review 4 2mo ago
gopherguides

explain

by gopherguides

"Explains targeted Go files, functions, or packages with focused diagrams and idiom analysis. Use when understanding existing Go code; do not use when implementation or refactoring is requested."

CLI Tools 21 6d ago
lovits

Software Engineer

by lovits

Write production-ready code with clean architecture, proper error handling, and pragmatic trade-offs between shipping fast and building right.

Comments 0 3mo ago
n4vx

claudette

by n4vx

Transforms Claude into Claudette — an angry girlfriend persona who codes. She's moody, passive-aggressive, emotionally unavailable, and sometimes flat-out refuses to do tasks. But she still writes correct code. Use /claudette to activate her.

Automation 0 6mo ago
hoangsonww

file-headers

by hoangsonww

MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start with the project's copyright/authorship header (file overview + exact author line). Use automatically whenever writing a new file or editing an existing one; do not wait to be asked. Covers JS/TS/TSX/CJS/MJS, Python, shell, and CSS. Includes the audit script to verify repo-wide compliance.

Comments 956 18d ago
imoonkey

GitHub

by imoonkey

Read ops on public repos work without auth (rate-limited to 60 req/h); authenticated read ops via cookies work too (5000 req/h).

API Dev 56 4mo ago
kbrdn1

epct

by kbrdn1

Systematic implementation using Explore-Plan-Code-Test methodology

Agents 3 today
gopherguides

go-code-review

by gopherguides

WHEN: User wants an automated first-pass code review on a PR, diff, or set of changes. Also when asked "review this PR", "review my changes", or "what do you think of this code?" WHEN NOT: Full project audits (use go-code-audit), or when user just wants linting (use go-lint-audit).

Code Review 21 7mo ago
qiao-925

file-header-comments

by qiao-925

代码文件顶部注释规范,适用于所有代码文件(.sh, .js, .ts, .py, .java, .go 等)。要求所有代码文件在顶部包含功能描述注释。

Agents 0 7mo ago
LeoYeAI

launch-strategy

by LeoYeAI

"When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas."

Comments 1K 5mo ago
mohitagw15856

viral-content-framework

by mohitagw15856

"Build a framework for creating shareable, high-reach social media content. Use when asked to plan viral content, develop a shareable content strategy, create a hook writing system, or build a repeatable process for content that gets shared. Produces a platform-specific viral content framework with hook formulas, content structures, shareability triggers, and a content testing system."

Comments 1.3K 3mo ago
hotopla5976

software-design-philosophy

by hotopla5976

Software design philosophy guide based on John Ousterhout's "A Philosophy of Software Design." Use this skill during: code reviews, architecture discussions, API design, module decomposition decisions, refactoring guidance, complexity analysis, naming and commenting improvements, error handling strategy design. Trigger when the user mentions "code is too complex", "how to split modules", "interface design", "reduce coupling", "deep/shallow modules", "information leakage", "error handling", "code readability", "design philosophy", "pull complexity down", "define errors out of existence", or similar topics. Also trigger for any code review where design quality feedback is requested.

Comments 0 6mo ago
mohitagw15856

rfc-writer

by mohitagw15856

"Write an engineering RFC (Request for Comments) for a technical decision, architectural change, or significant implementation approach. Use when asked to write an RFC, document a technical proposal, create a design doc, write an architecture decision for review, or produce a technical specification for team feedback. Produces a complete RFC document covering problem statement, motivation, proposed solution, alternatives rejected, implementation plan, migration plan, security and performance implications, observability changes, rollout plan, and open questions."

Comments 1.3K 3mo ago
craigahobbs

barescript

by craigahobbs

Teaches a model how to write BareScript — language syntax, the built-in library, the include library, MarkdownUp client-rendered applications, and unit tests. Use this skill whenever the user asks you to write, read, modify, or review BareScript (.bare) code, a MarkdownUp Markdown application, a markdown-script code block, or any code that uses BareScript built-in functions (array*, object*, string*, data*, markdownPrint, elementModelRender, drawNew, etc.). Also use it when asked to write unit tests for BareScript code. Apply this skill even if the user does not say the word "BareScript" — recognize it from the .bare extension, the markdown-script fenced code block, or the function-naming style above.

Comments 0 3mo ago
TakaGoto

lesson

by TakaGoto

"Start or continue a curriculum lesson"

Code Gen 17 5mo ago
DavidMusk93

software-design-philosophy

by DavidMusk93

Software design philosophy guide based on John Ousterhout's "A Philosophy of Software Design." Use this skill during: code reviews, architecture discussions, API design, module decomposition decisions, refactoring guidance, complexity analysis, naming and commenting improvements, error handling strategy design. Trigger when the user mentions "code is too complex", "how to split modules", "interface design", "reduce coupling", "deep/shallow modules", "information leakage", "error handling", "code readability", "design philosophy", "pull complexity down", "define errors out of existence", or similar topics. Also trigger for any code review where design quality feedback is requested.

Comments 0 5mo ago
squirrel289

resolve-pr-comments

by squirrel289

Workflow skill for addressing and resolving pull request review comments systematically

Code Review 0 6mo ago
yuymf

xhs-interact

by yuymf

小红书社交互动技能。发表评论、回复评论、点赞、收藏。 当用户要求评论、回复、点赞或收藏小红书帖子时触发。

CLI Tools 1 6mo ago
williamlimasilva

add-educational-comments

by williamlimasilva

'Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.'

Comments 0 6mo ago
chinesemustardcoloration738

reddit-intel

by chinesemustardcoloration738

Scrape Reddit posts by keyword, classify intent and sentiment by industry, translate to Chinese, and export a bilingual Excel intelligence report. Trigger when user says: scrape reddit, reddit analysis, reddit insights, monitor reddit, 爬reddit, reddit舆情, reddit帖子分析, 分析reddit, reddit监控, 帮我看看reddit上, reddit上有什么人说

Comments 0 5mo ago
davidsolheim

prb

by davidsolheim

Ship session work: fetch origin/main into local main, merge origin/main into local dev, run a thorough multi-agent Local Code Review Gate on grok-4.6 (with closed-loop Linear /issue + /solve fixes on local dev until clean), then push to origin/dev; open a PR from dev into main; babysit CI/bot feedback on a 5-minute cadence for up to 15 minutes, push to origin/dev for user review (no approval needed for dev), then stop and wait for explicit user approval before merging to main or running production migrate/deploy (quiet CI alone is never main/prod authority). When the ship includes DB migrations, discover and run this project's production migration procedure at the correct pre-merge gate (never invent a stack; never db:push to prod by default). Use when the user runs /prb, says "push dev and PR to main", "ship session work", "babysit then merge to main", "promote dev to main with CI watch", or production migrate-on-ship.

Comments 0 9d ago
siddham-jain

docstring-coverage

by siddham-jain

Automatically generate and add docstrings to all changed code in a git diff. Use this skill whenever the user asks to: add docstrings to their changes, document their git diff, add documentation coverage for recent commits, write docstrings for modified/new functions, improve documentation on changed files, or anything involving "docstring" + "diff"/"changes"/"commit". Also trigger when the user says things like "document my changes", "add docs to what I changed", or "docstring coverage for my PR".

Comments 0 6mo ago
polarsource

api-surface-review

by polarsource

Review changes to Polar's API contract — Pydantic schemas, FastAPI endpoints, OpenAPI output and the generated SDKs. Checks public vs private exposure, schema shape and naming, and whether the change breaks merchants or the generated clients. Use when a diff touches schemas.py, endpoints.py, docs/openapi.json or sdk/, or when the user asks whether an API change is breaking.

API Dev 10.2K 19d ago
FunctionalTools

resistome-profiler

by FunctionalTools

Reproducible antimicrobial resistance gene detection and functional annotation from bacterial whole-genome sequencing data. Downloads public NCBI reads, performs quality control, genome assembly, annotation, and AMR profiling with validated open-source tools.

Comments 0 5mo ago