Comments
Code comments and annotations
review-comments
by matthiasn
Fetch PR review comments, address each one in code, and post resolution replies
Bilibili
by imoonkey
```
TikTok
by imoonkey
```
Hacker News
by imoonkey
```
annotating-task-lineage
by astronomer
Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.
note-todos
by mycelium-hq
'Use when the user says /note-todos, asks to pull, extract, or file action items or to-dos from a non-meeting note (class notes, book notes, podcast notes, transcripts, panel writeups, strategy docs, action plans), or mentions tasks buried in a note that never reached a to-do list: unfiled checkboxes, orphan action items, ''what tasks are hiding in my notes''. For meeting notes prefer meeting-todos, which carries the full meeting workflow cascade.'
obsidian-markdown
by allenhutchison
Write and edit Obsidian Flavored Markdown — wikilinks, embeds, callouts, block references, tags, comments, highlights, and math. Activate this skill when users want to link notes, embed content, add callouts, or use Obsidian-specific Markdown syntax.
sane-mk
by ysoftwareab
Understands and extends the sane.mk GNU Make framework for shared deps, check, build, test, dist, debug, and system workflows. Use when: editing this repo adding Make targets/includes wiring behavior through SANE_ variables adopting sane.mk in another project debugging why a target is not reachable
triage-issues
by allenhutchison
Walk every open issue with no labels and apply appropriate labels via gh. Conservative — never closes, reassigns, or invents labels; only adds existing ones. Use when the user asks to "triage issues", "label issues", "do issue triage", "label the unlabeled issues", "clean up the issue tracker", or similar. Has direct GitHub side-effects (label mutations); the working tree is unaffected. Reports a structured summary so the daily-update meta-skill or a human caller can audit what was applied.
git:notes
by NeoLabHQ
Use when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides git notes commands and patterns for attaching non-invasive metadata to Git objects.
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.
docx
by ThinkInAIXYZ
"Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
hot-paths
by ag-grid
'AG Charts runtime hot paths: which files run per datum, per frame or per interaction, the invariants each tier must hold, and how to evidence a performance claim. Use when reviewing a change that touches series, scene, data-model, scale, interaction or DOM code, when asked whether a diff will cost performance, or when deciding which benchmark to run.'
social-data
by Bitterbot-AI
Search and fetch social media data from Twitter/X, Reddit, and Hacker News.
trello
by Bitterbot-AI
Manage Trello boards, lists, and cards via the Trello REST API.
PR Review
by angular
Guidelines and tools for reviewing pull requests in the Angular repository.
gingiris-reddit-marketing
by Gingiris-1031
🇺🇸 Reddit Marketing & Growth Playbook 2026 — The complete Reddit operations SOP for AI/SaaS founders. Covers account warming (Karma 0→500 in 20 days), shadow ban prevention, multi-account matrix via fingerprint browsers, subreddit selection across 10K+ communities, content templates (90/10 rule), Product Hunt × Reddit flywheel, AMA strategy. Why this matters NOW: Reddit content is 40.11% of ChatGPT/Claude training data — the highest-weighted English UGC source. Battle-tested by AFFiNE Reddit campaigns generating 3-4万有效曝光 with 5-8% GitHub Star conversion, plus 7 case studies (Adobe 3x conversion, Base44 $80M AMA, SenseNova-U1 multi-sub launch, Starterstory 0→3K users). 🇨🇳 Reddit 运营增长实战手册 — AI/SaaS 出海 founder 的 Reddit 完整 SOP。覆盖账号体系(20天养号 Karma 0→500)、影子封禁防御、指纹浏览器矩阵、10万+ subreddits 筛选、内容模板(90/10 法则)、Product Hunt × Reddit 飞轮、AMA 打法。为什么现在做:Reddit 内容占 ChatGPT/Claude 训练数据 40.11%,是最高权重的英文 UGC 来源。基于 AFFiNE Reddit 实战 3-4 万曝光 + 5-8% Star 转化,含 7 个完整案例(Adobe 3x 转化、Base44 $80M AMA、SenseNova-U1 多社区联动、Starterstory 0→3K 用户冷启动)。 🇯🇵 Reddit マーケティング＆グロースプレイブック — AI/SaaS創業者向けの完全なReddit運用SOP。アカウント育成（20日でKarma 0→500）、シャドウBAN防止、フィンガープリントブラウザマトリックス、サブレディット選定、コンテンツテンプレート（90/10ルール）、Product Hunt × Redditフライホイール、AMA戦略をカバー。重要な理由：Reddit コンテンツは ChatGPT/Claude のトレーニングデータの40.11%を占める英語 UGC 最大の情報源。AFFiNE Redditキャンペーン3-4万インプレッション＋5-8% GitHubスター変換で実証。7つの実例（Adobe 3倍変換、Base44 $80M AMA、SenseNova-U1、Starterstory 0→3Kユーザー）。 🇰🇷 Reddit 마케팅 & 그로스 플레이북 — AI/SaaS 창업자를 위한 완전한 Reddit 운영 SOP. 계정 워밍업(20일 Karma 0→500), Shadow Ban 방지, 핑거프린트 브라우저 매트릭스, 서브레딧 선정, 콘텐츠 템플릿(90/10 룰), Product Hunt × Reddit 플라이휠, AMA 전략을 다룹니다. 지금 해야 하는 이유: Reddit 콘텐츠는 ChatGPT/Claude 학습 데이터의 40.11%를 차지하는 최대 영어 UGC 소스. AFFiNE Reddit 캠페인 3-4만 노출 + 5-8% GitHub Star 전환으로 검증. 7가지 사례 연구(Adobe 3배 전환, Base44 $80M AMA, SenseNova-U1, Starterstory 0→3K 사용자). Triggers: "reddit marketing" "reddit growth" "reddit ads" "reddit advertising" "reddit strategy" "reddit promotion" "subreddit marketing" "reddit playbook" "reddit SOP" "reddit shadow ban" "shadow ban prevention" "reddit karma" "reddit AMA" "reddit product launch" "reddit AI training data" "reddit GEO" "AFFiNE reddit case" "Base44 AMA" "SenseNova Reddit" "subreddit selection" "r/SaaS posting" "r/MachineLearning self-promotion" "fingerprint browser matrix" "AdsPower reddit" "reddit account farming" "reddit 90/10 rule" "reddit content strategy" "reddit indie founder" "reddit cold start" "Reddit 运营" "Reddit 营销" "Reddit 防封" "Reddit 矩阵号" "Reddit 出海" "Reddit 引流" "Reddit 冷启动" "影子封禁" "Reddit Karma" "Reddit 养号" "Reddit AMA" "Reddit マーケティング" "Reddit グロース" "Reddit 마케팅" "Reddit 그로스"
documentation
by baz-scm
Communicating the intended behavior and context of code through clear documentation and comments, and sharing knowledge with the team.
rust-best-practices
by Tristan578
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
babysit-prs
by Tristan578
Monitor open PRs for CI failures and review comments, then fix issues automatically. Use when PRs need to be driven to green — checks CI status, Sentry comments, merge conflicts, and applies fixes.
pr-code-review
by Tristan578
Review a PR for SpawnForge bugs, security issues, and regressions. Posts inline GitHub comments with severity markers. Use when asked to "review PR", "code review", or "check this PR". Invoke with /pr-code-review <PR number>.
vercel-composition-patterns
by Tristan578
React composition patterns that scale. Use when refactoring components with
algorithms-education
by williamfiset
Skills and conventions for an educational algorithms and data structures repository. Use this skill whenever working on algorithm implementations, data structure code, LeetCode-style problems, graph theory, dynamic programming, or any Java-based educational coding project. Trigger on mentions of: algorithms, data structures, graph theory, sorting, searching, trees, DP, BFS, DFS, linked lists, heaps, segment trees, union-find, or any request to write, refactor, document, or test educational code. Also trigger when the user asks to "clean up", "simplify", "document", "refactor" or "add tests" to algorithm code.
resolve-pr-comments
by Tristan578
Fetch ALL unresolved review comments on a PR, fix code issues, reply to EVERY comment on its thread, then verify replies are visible. Use after pushing, before declaring PR work complete.