Testing lens for Orleans — spec-derived oracles, example tests, Accordant model-based tests, CsCheck property-based tests, deterministic simulation with controlled time, fault injection, and Verify snapshots. Use during code review, and when planning or writing tests.
6 projects use a version of this
11k12d agoReviewMountCreate a free account to mount
AWS CDK test-coverage reviewer. Use when a PR adds or changes tests (`**/*.test.ts`, `integ.*.ts`, `*.snapshot`) or ships new functionality, branches, feature-flag states, CFN properties, or cross-service behavior that should be tested — deciding first what coverage each change OWES (a unit test? an integ test? both? already covered? exempt?), then judging whether the PR's tests DISCHARGE it: meaningful assertions over non-asserting tests, edge/negative/feature-flag cases, required integ tests, snapshot-as-synthesized-template diffs, deploy-time assertions, and legitimate exemptions.
13k18d agoReviewMountCreate a free account to mount
Review a diff that touches Polar's billing domain — subscriptions, cycles and crons, orders, billing entries, meters and usage, discounts, checkout, payments and dunning, refunds, disputes, payouts, wallets, tax and invoices. Use before opening a PR that changes money movement or subscription lifecycle, when the user asks for a billing review, or when a reviewer needs the domain rules the team enforces in review but that no linter catches.
No other project uses it yet
10k9d agoReviewMountCreate a free account to mount
Shallow (quick) ensemble bug-finding review using 6 specialist agents in parallel. Each specialist reviews the same patch through a different lens: Logic & Types, Boundaries & I/O, Concurrency & State, Resources & Serialization, Absence Analysis, and API Completeness. Findings are merged and deduplicated. Best for: quick first-pass review of patches, triage of diffs, broad surface-level bug scan. For deeper file-focused review with full pattern catalogs and codebase investigation, use the deep-review skill instead.
10k5mo agoReviewMountCreate a free account to mount
Write a review document for a syft pull request. Takes a PR number or URL, reads the diff, and produces a checkbox-structured summary of the flows that changed with the new and changed code under each, the tests, and any code-standards problems in the new code. Use when the user says "review PR 1234", "write me a review doc for <PR link>", or "what changed in this PR".
10k18d agoReviewMountCreate a free account to mount
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.
Review Langfuse changes for SSRF, tenant isolation, secret handling, unsafe redirects or uploads, RBAC drift, and client telemetry privacy. Use when a design or change accepts URLs or host fields, handles secrets or cross-tenant data, makes outbound requests, adds an integration, follows redirects, widens permissions, or can send customer-controlled UI data through analytics, monitoring, or session replay.
Stage-by-stage pipeline health check - coverage, aging, conversion, and at-risk deals - from CRM opportunity data. Use when the user asks "review my pipeline", "pipeline health", "where's my pipeline stuck", "weekly pipeline review", "which deals should I focus on this week", "any stale or stuck deals", "which deals have past close dates", "which deals are single-threaded", or "check my pipeline coverage against my number".
Steady8 mentions in 2 weeks
13 projects use a version of this
35k10mo agoReviewMountCreate a free account to mount
Analyze recently closed opportunities to find patterns in what wins and what loses - stage of loss, common objections from transcripts, deal characteristics. Leader-focused. Use when the user asks "win loss review", "why are we losing deals", "what's working", or "analyze closed opps".
Steady8 mentions in 2 weeks
3 projects use a version of this
35k10mo agoReviewMountCreate a free account to mount
Watches what customers are saying in public and in private, then does something about it. Aggregates Google, Yelp, and Facebook reviews alongside disputes, tickets, and email into themes backed by verbatim quotes; drafts a reply to every review in the owner's own voice for approval; spots customers who have gone quiet or look likely to leave; and drafts win-back offers for the ones worth keeping. With Shopify connected, order and fulfillment patterns become a sentiment signal too. Works from pasted or exported reviews when nothing is connected. Use this whenever the owner asks about reviews, ratings, reputation, complaints, or repeat business — including "what are people saying about us," "did we get any bad reviews," "how do I respond to this one-star," "our rating dropped," "which customers have gone quiet," "who hasn't ordered in a while," "how do I win them back," or "are customers happy."
Steady8 mentions in 2 weeks
1 project uses a version of this
35k10mo agoReviewMountCreate a free account to mount
Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review — abstraction quality, giant files, and spaghetti-condition growth.
Review Paperclip stories for a feature or change using the Storybook catalog, production source, and existing browser tests. Report component, mock, interaction, and visual evidence separately.
Steady15 mentions in 2 weeks
No other project uses it yet
112k7d agoReviewMountCreate a free account to mount
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.
69 projects use a version of this
21k6d agoReviewMountCreate a free account to mount
Review a draft post, article or video script for a daily.dev for Startups company against the squad's weekly intel from daily.dev. Says what works, what's missing and how to improve it for developers who read daily.dev. Use when the user asks for feedback on a draft, a title or a script.
Steady11 mentions in 2 weeks
No other project uses it yet
20k9mo agoReviewMountCreate a free account to mount
Plan review criteria — the six review axes, severity rubric, approval standard, and output format for reviewing implementation plans. Loaded by the reviewer subagent of the review-plan flow. Not a user-facing flow — to review a plan, use the review-plan flow.
Steady6 mentions in 2 weeks
No other project uses it yet
62k2mo agoReviewMountCreate a free account to mount
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.