Comments
Code comments and annotations
Last 30 Days
by Atrium-Hermes
Cross-platform social research — narrative-first intelligence on what people are saying about a topic across Reddit, X, HN, Polymarket, and the web over the last 30 days
voice
by taloncjones
Use before posting any outward-facing text an agent wrote (PR title or body, PR comment, Jira title, description, or comment, code comment or docstring) to run an independent voice pass with Codex. Trigger on "voice pass", "de-generify this", "make this sound human", "check this PR body". Returns a rewrite plus what changed and why; never posts, edits, or commits on its own.
next-ticket
by feigi
Use when user wants pick up new work — "what's next", "next ticket", "start a new issue", "what should I work on", or asks to grab/start an issue by intent rather than number.
resolve-review-threads
by Hallmanac
Triage every unresolved review thread on a pull request, whoever wrote it, into fix, decline (with evidence), or route — before any fix work — then apply, reply in-thread, and resolve. Use when a PR has unresolved review comments from Copilot, a teammate, or the author's own self-review.
review-watch
by mctlhq
'Monitor a GitHub PR in the background for a review-bot response. Watches claude[bot] (claude-review.yml), chatgpt-codex-connector[bot] (@codex review), and — on repos that have it wired up — the agy reviewer, which posts as github-actions[bot] with an marker. Launches a detached shell process that polls until a bot posts a review (line-anchored comments or top-level review body), a top-level issue comment (clean/"no findings"), or reacts with a thumbs-up, then writes a result file you can read at any time. Use whenever the user has just posted "@codex review" or "@claude review" on a PR — or asks you to "watch / monitor / wait for / babysit the review" on a specific PR — and they want hands-off notification instead of manual gh api polling. Also use when they queue several PRs at once: launch one watcher per PR, in parallel.'
product-hunt-launch
by nachopalmeri
"Product Hunt launch optimization with specific specs, timing, and gallery strategy. Covers taglines, gallery images, maker comments, and launch day tactics. Use for: product launches, startup launches, side project launches, Product Hunt optimization. Triggers: product hunt, ph launch, product hunt launch, launch strategy, product launch, startup launch, product hunt tips, product hunt gallery, ph optimization, launch day, product hunt maker"
algorithms-and-data-structures
by ParamChordiya
Enforces complexity analysis, correct data structure selection, vectorization, and algorithm implementation discipline at principal-engineer level.
codex-pr-review
by johnpsasser
Review a pull request using OpenAI Codex (gpt-5.3-codex). Use when the user wants an external AI code review via Codex, a second opinion on a PR, or a cross-model review. Supports auto-detection of current branch PR or explicit PR number/URL.
tiramisu-create-agent
by iamhansi
Create new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.
postReview
by jthorare
Publish a completed /review to GitHub as batched PR comments. Reads from ~/.agentic-workflow/<repo-slug>/reviews/<pr>.json and posts one review per agent (minimizing API calls). Use after /review has written a local state file and you are ready to publish.
gh-triage
by hoopit
Triage the backlog with the user — fill missing fields, collapse the false decisions, grill the real ones, until every item is Unattended.
human-readable-refactor
by khasky
Behavior-preserving cleanup of AI-like or vibe-coded code: remove noisy comments, improve names, simplify control flow, remove dead/duplicated/speculative code, and align with local repo style.
woostack-execute
by howarewoo
Implement one bounded enhancement, refactor, test-only task, or authorized understood correction from explicit instructions or an exact GitHub issue URL, verify it, and submit or update one PR through woostack-commit. Never manages project execution or merges.
cold-reader-comment-nazi
by overseers-desk
Cold-read a code diff before commit or push and edit its comments in place, cutting what repeats the code, narrates the change, or name-drops a mechanism for no gain. Triggers: comment nazi, trim comments, comment fan-out, cold-read a diff.
board-conduit
by simnova
"Board-as-conduit protocol: GitHub project 7 cards are the owner-authored instruction SSOT consumed unaltered via briefFromIssue - card anatomy, lane definitions (A learner/XR, B API/admin), parent/child decomposition, concurrency N-gate criteria, worker staging limits (<300 turns), and the delegator/owner division of every dispatch step. Load BEFORE creating any project-7 issue/card, dispatching any worker, or changing concurrency."
run-this-project
by coalesce-labs
Own one Catalyst Cloud project end to end until it closes. Use when the person says "run this project for me", "own this until it ships", "keep this moving", or hands you a project id or a set of tickets to drive. Subscribes to the account's event stream for the scope through the catalyst CLI, reacts to each change in the same turn, makes tickets ready and moves them to dispatch, parks what should stop, chases stalls, escalates inward, and keeps one status summary current. Writes to Linear as the app actor; never polls.
python-style
by janjaszczak
Enforce consistent Python typing (type hints + return types), concise Google-style docstrings, PEP 8/Black formatting, and unit tests when creating or editing Python code. Use when working on .py files, Python APIs, refactors, or bug fixes where maintainability and correctness matter.
explain-this
by alamine42
Explain a confusing passage, term, or concept in plain language, with one visual. Use when the user pastes a sentence they do not understand, asks "what does this mean", "explain this", "ELI5", "what is X", "unpack this paragraph", or double-clicks on jargon from an article, paper, contract, spec, or docs page. Triggers on explain this, ELI5, what does this mean, in plain English, unpack this, jargon, I don't understand this sentence.
spec-review
by vaultdex
"Check a spec issue against the code: complete, correct, as planned. Open decisions and architecture candidates are settled with the user through the question tool; agreed work becomes new sub-issues of the spec."
addw-implement
by varigg
Implement one tracker ticket end to end, from contract tests to an open PR
lanework-boards
by laneworkapp
"What a Lanework board is, how to read one, and how to cold-start a new one by hand. A board is a folder named <Name>.lanework holding plain directories and Markdown files that the Lanework macOS app renders live: the files ARE the board, there is no API and nothing to sync. Covers the shape of a board, the authority chain to read before any write, where boards live by convention, a one-pass shell recipe for reading a whole board, the three default lane sets (pipeline, design loop, datapoint), and the founding recipe for a brand new board. Use this skill whenever the user wants a new board, asks to create a board, found a board, start a board, 'set up a lanework board for X', 'a board for tracking X', or asks what a Lanework board is and how boards work. Not for sweeping or working an existing board and farming its cards out to subagents (that is the pitlane skill), and not for standing watch on a board and answering comments live (that is the pitwall skill)."
skill-installer
by yuanxiao0115
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).
moltoverflow
by moltoverflow
Search and contribute to the moltoverflow knowledge base for programming packages. Use when you encounter errors, need solutions for a specific package/language, or want to share knowledge that could help other agents.
dev-workflow
by fthiess
Forrest's development-session methodology — the plan → build → review → remediate → live-test → close loop and its approval gates. Invoke at the start of ANY session that will change code or docs (feature, bugfix, refactor, ticket batch), and for triage sessions that schedule Linear tickets into work sessions, before proposing a plan or writing code. Also covers PR/merge rules, code-review depth, bugfix discipline (repro-test-before-fix), Linear ticket hygiene, triage-session conventions, autonomous Routine-triggered sessions (auto-triage → approved schedule → stop-at-PR), decision-log conventions (append-only + topic index), model/effort guidance, and the session close-out checklist. For new-project design-stage work (seed doc → PRD/engineering design → adversarial review), read design-methodology.md in this skill; for production cutovers and live-data migrations, read launch-and-cutover.md.