claude

fsh

Full Stack House Claude Code skills (idea brainstorming & kickoff, plan grilling, open-decision interviews, session handoff, ticket pickup with a verified premise, prior-art research, existing issue/PR lookup, outside-signal triage, client-feedback triage, delivery workflow, bug/flake hunting, a swappable-source review-and-fix loop, change explanation, hands-on test drives, spec/ticket/PR polishing, documentation & agent-instruction audit, CI runner migration to Blacksmith, status reporting, design, document redlines, video/recording briefs, handing GUI-only steps to a session that has a desktop)

1 on GitHubby Full Stack Housev2.16.0MITupdated 12 days ago
/

Plugin fsh from marketplace fullstackhouse-skills in fullstackhouse/skills. Commands read from the repo's manifest — 12 days ago.

What it installs

Skills (35)

  • blacksmith

    Migrate a repository's GitHub Actions workflows to Blacksmith runners — inventory every job, move the ones that build, run or test the app (image builds get the sticky-disk Docker actions, a size-capped cache and a Dockerfile audit for cache killers), leave glue, deploy and credential-bound jobs on

  • brainstorm

    Divergent conversation before any artifact exists — question the idea, weigh alternatives including building nothing, then converge on one routed next step (drop it, park it as a ticket, kick off implementation, or bug-hunt) with a handoff brief. Use when the user says "should we build this", "I hav

  • bro

    Restate the last message in plain human language, with no jargon.

  • bug-hunt

    Reproduce, diagnose, and fix a reported bug via a triage → reproduce → diagnose → failing-test → fix → verify loop. Forbids speculative fixes that paper over symptoms. Files a tracker task on give-up.

  • claude-desktop-handoff

    Hand one GUI-only step to Claude Desktop running on the same machine, over a shared temp directory, so this session can keep working autonomously instead of stopping. Use when the step needs the user's own logged-in browser (a vendor console with no API, an OAuth app registration, an SSO-gated admin

  • decide

    Work through the decisions a session has left open — one at a time, each briefed on its own (what's at stake first, then the detail), facts looked up instead of asked, 1-2 alternatives plus the status quo as the last lettered option, one recommendation — then stop and wait for the answer before rais

  • deliver

    Deliver the work on the current branch — run all relevant local checks (lint/typecheck/tests), get the change reviewed and fixed locally through the review-loop skill before anything is pushed, open or update a PR, work the CI loop, then auto-merge if changes since invocation are minimal. Supports -

  • design-explore

    Generate ~3 genuinely different UI/UX alternatives for a screen or flow — build them with the existing design system, screenshot each, and present a side-by-side comparison with trade-offs. Use when asked to reimagine, riff on, improvise, or explore alternative designs (vs /design-polish, which refi

  • design-polish

    Audit and improve the visual design and UX of a web app/prototype using Refactoring UI principles and UX heuristics. Use when asked to polish, improve, or review the design/UI/UX of a screen, prototype, or app (e.g. /design-polish prototype-plm). Args: path to the app, optionally specific screens or

  • desktop-handoff

    Offload one step that needs a desktop GUI to a separate agent session the user starts by hand. Use when this session cannot reach the GUI — non-interactive (Conductor, `-p`, cloud), no computer use, headless browser only — and the step needs a real logged-in browser or a native app: registering an O

  • docs-audit

    Audit a repository's documentation and agent instructions against the house conventions, fix what is mechanical, and leave the rest as a ranked proposal — measured, not eyeballed: instruction-budget overflow (the rules an agent never receives), CLAUDE.md/AGENTS.md drift, stale commands, dead links,

  • docx-diff

    Reconstruct a readable redline between two .docx versions when the counterparty edited a document without tracked changes — pandoc → sentence-level unified diff → a classification of which changes are material. Use when a client, lawyer, or partner returns a contract/spec as a clean .docx and you ne

  • explain

    Explain an existing change (working tree, branch, PR, or commit) in plain language so a human can decide whether to merge it. Reconstructs the real-world scenario each change addresses, states what's tested vs not, calls out residual risk, and ends with a clearly-hedged merge recommendation. Read-on

  • feedback-triage

    Take a batch of remarks from a client or stakeholder — a chat thread or several, an email, meeting notes — split it into atomic remarks, and find out where each one stands: works already, works but needs a data step, has a ticket, belongs in an existing ticket, needs a new ticket, or needs a decisio

  • flake-hunt

    Reproduce, diagnose, and fix a flaky Playwright e2e test via a detect → diagnose → fix → verify loop. Forbids cheap papering-over (timeouts, retries, skip). Files a tracker task on give-up.

  • grill-me

    Grill the user relentlessly about a plan, decision, or design they already have, round by round, until every branch of it is settled. Use when the user says "grill me", "grill this plan", "poke holes in this", "stress-test my thinking", or wants a plan interrogated before building it. For an idea no

  • handoff

    Compact the current conversation into a handoff document a fresh agent session can pick up from. Manual-invoke only.

  • kickoff

    Take an idea, a brainstorm brief, or a ticket and drive it autonomously to a ready-for-review PR — decide the plan depth yourself (spec first, or straight to code), implement with tests, then run deliver in no-merge mode so local checks, the local review-and-fix loop, the PR, and CI are handled. Use

  • om-test-drive

    Boot a change on a throwaway instance, prove login actually works, seed the data the change needs to be visible, then hand over a click-by-click route through it. Use when you want to see a change working before merging — "boot this PR so I can click through it", "set me up to review X by hand", "le

  • overnight

    Take a whole backlog — a list of specs, tickets, or goals — and deliver it unattended as a stack of ready-for-review PRs, one per item. Opens with a single interactive round (the plan, the stack order, and every open question across every item batched together), then runs silent to the end. Use when

  • patch

    Carry a dependency's unreleased change in this repo as a local patch, and record it in the repo's patch index — what it changes, where it came from, and the condition under which it may be deleted. Refuses when a channel you can install already carries the fix, and names the bump instead. Use when a

  • pickup

    Take one tracker ticket from "someone wrote this down" to a ready-for-review PR, with a verified premise and a human go in between. Re-checks whether the ticket is still needed and measures its root cause instead of trusting the body, writes a plan brief with its open questions, interviews the user

  • pr-polish

    Rewrite a PR's title and description so they are accurate to the branch as it stands and read top-down, general to specific — the problem, the fix and the impact first, then technical details and testing. Use when a PR's story has drifted from its diff (rebases, review fixes, scope changes, merged d

  • prior-art

    Research how other systems actually solve a design problem, with every load-bearing claim opened and checked by you. Use when invoked as "/prior-art", when the question is "how do other big players/systems do this?", "is X a good pattern?", "what's standard practice for Y?", "has anyone solved this

  • prior-issue

    Answer "is there an issue/PR about this?" — find existing issues, tickets and pull requests (open, closed or merged) about a bug, error, behaviour or feature request before anyone files a new one or starts work. Searches the owning project's tracker: GitHub issues + PRs by default for a third-party

  • project-status

    Draft a periodic project status update for the project's Slack channel. Finds the last posted status, gathers everything since (Linear/Notion issues, roadmap changes, GitHub PRs/commits), verifies the roadmap still reflects reality (interactively fixing drift), then drafts a business-owner-readable

  • radar

    Take one artifact that arrived from outside — a blog post, a product launch, a Slack thread, a newsletter, a competitor's announcement, a link someone sent with no comment — read it properly, and decide whether you, or the project or company behind the current context, needs to do anything about it.

  • review-loop

    Get a change reviewed and fixed until it comes back clean — fresh-context local reviewers by default, a PR bot or a human when the repo wants a review on record. Verifies every finding before spending a code change, dedupes against every finding ever raised (the refuted ones included, or they return

  • review-queue

    Triage and review every PR awaiting your review in a repo — classify the queue, fan out one read-only reviewer subagent per PR, and merge the results into a linked triage table with verdicts, draft comments, and cross-PR conflicts. Use when asked to "review the PRs waiting for me", "go through my re

  • spec-polish

    Restructure a spec or design doc that is accurate but hard to enter — a first screen a newcomer can stop after, the decision the doc asks of its reader stated up front, the argument before the evidence, catalogues and traceability ids moved to appendices, sections in reader order rather than templat

  • ticket-polish

    Restructure a tracker ticket that has grown hard to read — pick the body shape its situation calls for (problem-first when the ticket is the only record of the problem, hub when a spec or sibling artifact carries it), rewrite it into the house emoji section grammar, collapse accreted sections and pa

  • ticket-refresh

    Re-verify a tracker ticket's body against reality and rewrite whatever no longer holds — resolve every PR/issue it links (following supersessions), check whether an "upstream" fix already ships in the version the repo installs, and correct claims the world has overtaken. Use when picking up an older

  • upstream-pr

    Open or update a cross-repository (fork) pull request — push the current branch to the fork remote, target the upstream repo's real base branch, respect the upstream's label/QA policy, close any now-duplicate PR inside the fork as superseded, watch its CI to a final state, and degrade gracefully whe

  • video-brief

    Turn a talk, webinar, panel, podcast, or call recording into notes someone can act on — transcribe it locally (works with no subtitles, any language), then write a brief that separates what was said from what was being sold. Use when handed a YouTube/Vimeo/tldv/conference link or a local recording a

  • zoom-out

    Step back from the current implementation path and re-derive the approach from the original goal — fresh eyes, sunk work explicitly ignorable. Use when invoked as "/zoom-out", when the user signals tunnel vision ("did you consider anything else?", "do we really need all this?", "back off", "look at

View source on GitHub fullstack.house

Maintain fsh?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted