@Significant-Gravitas
Organization
311 skills2 repositories 187.7K
Review a pull request, a proposed code change, for correctness, security, design, and test coverage. Check its explanation and existing feedback, then post findings on relevant code lines with severity labels.
Compare performance across releases, environments, or time windows using Sentry data. Report request counts, latency percentiles, and failure rates, with statistical checks that distinguish faster or slower behavior from noise and flag insufficient data.
Improve React and Next.js performance when writing, reviewing, or refactoring code. Apply prioritized rules to reduce sequential data requests, shrink downloaded code, and improve server processing and component rendering.
Work through PR review feedback by fixing code, pushing commits, replying to reviewers, and resolving addressed threads. Monitor automated checks, merge conflicts, and new comments until checks pass and the review work is complete.
Prepare a pull request for merging by repeatedly reviewing changes and addressing feedback. Verify resolved discussions, passing automated checks, and mergeability, then check twice for late comments after the checks finish.
Review frontend changes against a base branch, propose a test plan, and write integration tests that check pages and components together. Cover user interactions and API responses, then run tests, formatting, lint, and type checks.
Prepare a separate development folder for a Git branch using a worktree. The skill copies environment files, installs Python and frontend dependencies, and generates the Prisma client so the branch has its own working setup.
Coordinate multiple Claude Code agents in separate Git worktrees and tmux windows. Assign tasks, inspect progress, help stalled agents resume, and verify PR checks and review feedback before treating work as complete.
Prepare a repository for parallel development with Git worktrees, separate folders for different branches. Create review and numbered work branches, copy environment files and branchlet configuration, and install dependencies for each workspace.
Create a pull request that follows the project's template and title conventions. Check existing behavior and test coverage, document testing limits, and coordinate self-review or bot review with follow-up on reported issues.
Test a PR or branch through a running application using browser actions and API calls. Compare expected behavior with actual state changes, include failure cases, and post a report with before-and-after screenshots to the PR.
Use when a strategic partner needs more than an annual plan: one, three, and five-year horizons, a capability scorecard, and executive governance.
The English summary is being prepared. Showing the original description.
Draft a procurement decision memo that shows requirements, total cost, evidence gaps, risks, and approvals without selecting or binding.
The English summary is being prepared. Showing the original description.
Compare written policies with a named framework's control list and show gaps with evidence.
The English summary is being prepared. Showing the original description.
Review a pitch deck for decision flow, source support, internal consistency, clear metrics, and safe investor claims.
The English summary is being prepared. Showing the original description.
Define each pipeline stage with an entry rule, an exit rule, and required proof.
The English summary is being prepared. Showing the original description.
Use when the user names pricing, packaging, tiers, or discounts, or hands over a price list, competitor pricing, or deal terms: the pricing recommendation with guardrails and mix impact.
The English summary is being prepared. Showing the original description.
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
The English summary is being prepared. Showing the original description.
Draft a press release with the news first, checkable claims, approved quotes, and a boilerplate.
The English summary is being prepared. Showing the original description.
Use when a partner QBR or business review is coming: grade the quarter against benchmarks, co-draft the agenda, ship the pre-read, land the recap.
The English summary is being prepared. Showing the original description.
Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B SaaS sales team from scratch or building a lead-qualification framework to improve close rates. Covers the three lead types (seeds/nets/spears), role specialization, the referral-email method, ANUM qualification, and pipeline math. For offer design, see hundred-million-offers. For persuasion science, see influence-psychology.
The English summary is being prepared. Showing the original description.
Prepare an internal approval brief for a price or term request, with policy position, business case, risks, give-get, and named approvers.
The English summary is being prepared. Showing the original description.
Use when the user names positioning, messaging, narrative, or value props, or hands over a draft to sharpen: the positioning doc and the message house per audience.
The English summary is being prepared. Showing the original description.
Track and analyze portfolio company performance against plan. Ingests monthly/quarterly financial packages (Excel, PDF), extracts KPIs, flags variances to budget, and produces summary dashboards. Use when reviewing portfolio company financials, preparing board materials, or monitoring covenant compliance. Triggers on "review portfolio company", "monthly financials", "how is [company] performing", "covenant check", or "portfolio update".
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)