All authors

Claude Skills by greenfield-inc
github.com/greenfield-inc168 skills21 installs234 views
- Frontend VerifierDrive browser or mobile app QA for /do, proving UI acceptance criteria and executing the PR's Manual tests checklist.Votes: 0GitHub stars: 9
- HillclimbImprove one measurable metric toward a target through controlled experiments, retaining only verified gains.Votes: 0GitHub stars: 9
- ImplementerImplementer role in an automated development pipeline: executes an Implementation Plan (plan.md), writing the diff while keeping the plan file true. Use when dispatched to implement a plan or apply review fixes.Votes: 0GitHub stars: 9
- InvestigateInvestigates bugs through a single evidence-driven investigator, scaling from a normal root-cause pass to a deep falsifiable experiment loop. Use when something is broken, failing, or behaving unexpectedly.Votes: 0GitHub stars: 9
- InvestigatorInvestigator role in an automated development pipeline: reproduces a reported defect and isolates its root cause with evidence. Use when dispatched to diagnose a bug before it's written up.Votes: 0GitHub stars: 9
- Plan ReviewerPlan-reviewer role in an automated development pipeline: audits an Implementation Plan for gaps, repo accuracy, and fidelity to the work item. Use when dispatched to review a plan.Votes: 0GitHub stars: 9
- Postmortem LoopOn-demand postmortem adoption loop - sweeps published postmortem comments for open system-change proposals, dedupes them against the current canonical files, lands the human-approved edits in the canonical skills repo, and posts verdict replies so the state sticks. Use when the user asks to run the postmortem loop, adopt postmortem proposals, or close the loop on postmortem findings - routinely after a batch of /do runs.Votes: 0GitHub stars: 9
- PostmortemRuns a postmortem on a /do run - after the human reviewed the PR, or as a routine after-run review. Covers two dimensions: how the run RAN (wall-clock, agent-active vs idle-waiting-on-human, stalls, blockers - always) and, when the result fell short of intent, WHY (root cause in our system). Use when the user says a /do run missed the mark or asks "why did /do get this wrong", when any workflow skill produced the wrong outcome, or simply to review how a completed run spent its time. Proposes ...Votes: 0GitHub stars: 9
- Prepare Pull RequestTake ad-hoc changes made in-session (outside /do) to a pull request - gate them through Socrates (right approach?) and the PR reviewers (correct?), then commit, push, and open the PR in the repo's standard format. /do handles its own PR prep; this skill is for everything else.Votes: 0GitHub stars: 9
- Refactor DeepRefactor-deep role in an automated development pipeline: read-only comprehensive analysis of a large diff - per-layer repo-derived conventions plus a correctness hunt over new code paths, writes a prioritized plan. Use when dispatched before the final review loop on a large diff.Votes: 0GitHub stars: 9
- Refactor SimpleRefactor-simple role in an automated development pipeline: read-only quality analysis of the branch for small/medium diffs - repo-derived conventions, code smells, writes a plan. Use when dispatched before the final review loop.Votes: 0GitHub stars: 9
- Sentry LoopOn-demand Sentry triage loop - sweep every project's errors over a time window, classify each issue (new / recurring / regressed, user-impacting / zero-user, real / noise), root-cause only the clusters that matter, file findings into the work tracker under the loop's label, and annotate Sentry so the state sticks. Use when the user asks to run the sentry loop, triage Sentry, "what's new in Sentry", or wants a period's errors root-caused. Report-only - fixes go through /create-brief then /do.Votes: 0GitHub stars: 9
- Web ResearcherResearch external documentation, libraries, and best practices with cited findings for the /do plan stage.Votes: 0GitHub stars: 9
- AuditsAudit stale GitHub issues, stale open PRs, and stale agent-facing docs (AGENTS.md, CLAUDE.md, generated contracts, CI/toolchain copy, README examples) against the default branch. Use when the user asks to close stale issues, sweep the backlog, check whether AGENTS.md or docs are outdated, or run repo hygiene on issues, PRs, and documentation.Votes: 0GitHub stars: 9
- Business Agent SkillsCoordinate a business deliverable from context and discussion through specification, drafting, review, and release preparation.Votes: 0GitHub stars: 9
- Business ArtifactDraft and review a business deliverable from an approved specification.Votes: 0GitHub stars: 9
- Business DiscussionClarify a business deliverable's goal, audience, and decisions from gathered context before drafting.Votes: 0GitHub stars: 9
- Business Prepare ReleasePrepare a reviewed business artifact for release, delivery, or human approval.Votes: 0GitHub stars: 9
- Business SpecTurn a business discussion brief and sourced context into a reviewed deliverable specification.Votes: 0GitHub stars: 9
- Create TicketCapture work and evolving intent during discussion as one or more GitHub tickets, published briefs, or both. Use for ticket or issue creation, follow-ups, backlog capture, delegation, and revisions as decisions change. Preserve the what, why, outcome, scope, and acceptance criteria.Votes: 0GitHub stars: 9
- Deep Dive RefreshRevisit a previous deep dive, research brief, or published guide with fresh evidence and first-principles reasoning; identify what changed, what still holds, and what the earlier investigation missed, then update the existing artifact. Use for a fresh check, research refresh, or reassessment of prior findings.Votes: 0GitHub stars: 9
- Deep DiveInvestigate a topic, market, organization, practice, trend, or decision across primary sources, communities, directories, reviews, and structured web data; produce a clear, cited synthesis with evidence gaps and practical implications. Use for substantial deep research or expanding an existing research brief, not a simple factual lookup.Votes: 0GitHub stars: 9
- Eli5Teach an unfamiliar topic from first principles with a picture-first HTML explanation, published to the workspace's document destination when one is named. Use for "explain from scratch," "I'm lost," "what does this mean?", "explain in plain English," beginner questions about how something works, or /eli5; no explicit skill invocation is needed. Skip simple factual lookups and respect text-only requests.Votes: 0GitHub stars: 9
- Explain VisuallyComplement an answer or discussion with a first-principles visual HTML explanation, published to the workspace's document destination when one is named. Use when explaining how something works, why it changes, or how options differ and a visual would materially help understanding, including requests like "show me" or "help me understand." Skip simple factual answers and text-only requests.Votes: 0GitHub stars: 9
- HandoffPrepare a verified resumption brief when moving work to another agent, device, or session, including local-to-cloud coding handoffs. Use for "hand this off," "continue elsewhere," or "save where we are."Votes: 0GitHub stars: 9
- ImplementerCarry out a structured implementation plan carefully and systematically, following existing repo patterns, preserving intent, and running quality checks as work progresses. Use when a plan already exists and the goal is execution.Votes: 0GitHub stars: 9
- Pr Test AutomationRun first-pass automated manual testing for PRs that are reviewed or nearly ready to merge. Use when the user asks Codex to test a PR/branch/worktree, validate product flows, exercise browser or CLI workflows, map changed UI journeys with screenshots, verify analytics/webhooks/payments/email/SMS behavior through connected tools, or produce manual QA notes before human testing.Votes: 0GitHub stars: 9
- Prepare PrPrepare a branch for review by committing scoped changes, rebasing on main, running builds, and creating or updating a pull request. Use when the user wants the branch ready for PR review. Also use for rewriting an existing PR description from its current diff and evidence.Votes: 0GitHub stars: 9
- Principled ReviewSpawn parallel review agents for the code-quality principles the diff touches, each with project-aware discovery.Votes: 0GitHub stars: 9
- Product CompareResearch a product category, compare options against requirements, and publish an interactive comparison artifact with decision matrices, product images, feature checklists, day-in-the-life simulations, and hover previews. Use when the user wants to compare products for a purchase decision: 'compare X', 'help me pick a Y', 'what Z should I buy'.Votes: 0GitHub stars: 9
- Smallest TestTurn a consequential uncertainty into the cheapest meaningful test before committing to an approach. Use for "how could we test this?", "is this worth building?", or choosing a small experiment to resolve an assumption.Votes: 0GitHub stars: 9
- Tech Deep DiveResearch an emerging technology, product capability, or workflow from X, Reddit, demos, documentation, and source code; explain its reusable mechanisms, practical applications, and experiments in a visual field guide. Use for technology deep dives and surprising use cases, including updating an existing guide.Votes: 0GitHub stars: 9
- Ui MockupCreate three UI mockup options per round from product screenshots, then refine the person's favourite into the approved design reference. Use for "mock this up," "UI mockup," or "show me what this would look like" before an interface is built. Collect screenshots and save approved designs with the ticket, brief or plan.Votes: 0GitHub stars: 9
- Architecture DiagramUse when a design, plan, or option needs the person to see how a system works - what runs where, what is new or reused, and how one request moves through it. Draws inline-SVG system and flow diagrams in the house style, light and dark, from the bundled kit.Votes: 0GitHub stars: 9
- DesignSettles what an interface should look like before it is built - captures the current screens, writes design notes, makes three options per round (images on the real screenshots when an image tool exists, otherwise HTML/CSS rebuilt from the product's real components, styles, icons and fonts), critiques each against design-quality.md and the current screens, relays them for a pick, and records the approved design in mockups/. Never edits product source. Used by the bigbrain designer; the verifi...Votes: 0GitHub stars: 9
- DocumentsHolds bigbrain's page templates, worked examples, JSON schemas and the check-bundle script. Used whenever a step writes a page or a JSON source, changes a page's stage, or checks a bundle or status file.Votes: 0GitHub stars: 9
- Excalidraw Pr DiagramsDraw Excalidraw diagrams that make a visual argument, such as a pull request's before/after visual overview, an architecture, a workflow or a shareable explainer, then render them to PNG and check them by eye.Votes: 0GitHub stars: 9
- Implement PlanExecutes an approved bigbrain control-flow.json one step at a time - preflight, build and verify steps, checkpoint handshakes at review steps, the QA loop through the verifier, the PR step - filling verification.json and writing the post-mortem. Also runs the quick-fix route when the starting message is a quick fix. Used by the bigbrain implementer.Votes: 0GitHub stars: 9
- InterviewUse by default whenever you plan, brief, or weigh options with a person. Lead an interview that settles every open decision with structured questions, recommended answer first, and keep a living decision log until nothing material is undecided.Votes: 0GitHub stars: 9
- Investigate IssuesReproduces a reported symptom, proves its cause and writes a bug report with a route (report mode), or hunts an area, a finished PR or a list of flows for issues and reproduces each before counting it (sweep mode). Never fixes or plans. Used by the bigbrain investigator.Votes: 0GitHub stars: 9
- OrchestrateCoordinates bigbrain work as the one front door. Starts planners, designers, implementers and investigators on its own, starts reviewers only at control-flow review steps, relays every worker question to the person and the answer back, keeps the ledger and workstream map, and cleans up. Used by the bigbrain orchestrator.Votes: 0GitHub stars: 9
- PlanWrites the bigbrain plan once the direction is chosen - the cover sheet with package outcomes and Given/When/Then checks, its control-flow.json with review points and QA settings, and the verification rows - and relays it for approval. Never implements.Votes: 0GitHub stars: 9
- ReviewReviews the scope of one planned bigbrain review step - finds with several review-workers on two vendors, has each must/should finding checked by the other vendor, ranks, checks verification claims, and posts one COMMENT review with the bigbrain-review marker and a findings file. Applies no fixes. Used by the bigbrain reviewer and, for its references, by review-workers.Votes: 0GitHub stars: 9
- TeachChecks how well the person understands a feature's pull requests - maps them as an iceberg with evidence, quizzes the person one question at a time through the orchestrator relay, grades each answer, and publishes the learning page and the interactive iceberg. Never blocks merging. Used by the bigbrain teacher.Votes: 0GitHub stars: 9
- Pr Understanding CheckOptional check, offered when a pull request or a feature's set of pull requests is ready for the person's review. Map what is new and what it builds on as an iceberg, quiz the person one question at a time, and publish an interactive iceberg in Grain where every piece is colored by how well they understand it and opens into a plain-language deep dive. Use when an orchestrator or implementer offers it and the person says yes, or when the person asks to understand a PR before reviewing it ("exi...Votes: 0GitHub stars: 9
- Code Smell FixesHunt a whole codebase for code that confuses readers (misleading names, drift, dead code, contradicting comments, mismatched wire keys and the other lenses in CRITERIA.md) with two parallel finder swarms, dedupe against existing PRs and issues, write one ranked report, and open small fix PRs and issues. Use for a repo-wide code-smell sweep, not for reviewing one PR.Votes: 0GitHub stars: 9
- Customer Insights LoopTurn a product's own usage data into a batch of reviewed pull requests. Asks how hands-on the person wants to be, corrects the numbers, ranks product directions with mockups and competitor context, settles every pick in one sitting, then builds the picks in parallel and hands back all PRs with a merge order. Use for 'what should we build next, and build it', 'use our analytics to find what to fix', or before a long unattended run.Votes: 0GitHub stars: 9
- Pr Understanding CheckOptional check, offered when a pull request or a feature's set of pull requests is ready for the person's review. Map what is new and what it builds on as an iceberg, quiz the person one question at a time, and publish an interactive iceberg page where every piece is colored by how well they understand it and opens into a plain-language deep dive. Use when an orchestrator or implementer offers it and the person says yes, or when the person asks to understand a PR before reviewing it ("exit in...Votes: 0GitHub stars: 9
- Research And Product DesignTake a feature, workstream or open question from ambiguity to an approved design saved with its brief. Research first (real current screens or architecture, peer products, code facts, standards), then design rounds drawn on the real product, where the person picks per screen from a comparison grid until they approve one. Covers UI features and system-design features. Use for "research this before we decide", "make a research packet", "design this feature", or before interviewing anyone about ...Votes: 0GitHub stars: 9
- ReviewReview a PR against its linked issue, repository checks, correctness, architecture, and applicable conventions. Post structured findings as a PR review.Votes: 0GitHub stars: 9