fzymgc-house-fzymgc-house-skills

Plugin fzymgc-house-fzymgc-house-skills from marketplace cascade-code-devops-misc-1 in joshuarweaver/cascade-code-devops-misc-1. Commands read from the repo's manifest — 1 month ago.

Skills (32)

• address-findings

  Processes findings from review-pr by working through beads in the review epic. Use when the user asks to "address review findings", "fix review issues", "work through review beads", or "process review findings". - Task - Read - Edit - Write - Grep - Glob - "Bash(test *)" - "Bash(git *)" - "Bash(jj s

• bead-create-smart

  Create a tracked bd issue using structured flags (per Rule 3) rather than an 8-section description heredoc. Use for ad-hoc beads outside the plan-to-beads materialization flow — reviewer findings, bug reports, follow-up beads at session close, or single tasks the user wants tracked. Accepts an optio

• brainstorming

  You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

• capture-adrs

  Use when the user has finalized a spec or plan and wants to extract ADR-worthy decisions into both `docs/adr/<bd-id>-<slug>.md` files AND `bd create -t decision` records. Triggered by `/capture-adrs <path>` or by the nudge-adr-capture hook's reminder. NOT for general ADR audit — use the adr-extracto

• dispatching-parallel-agents

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

• drain-with-worker

  Launch an autonomous /drain worker in a detached cmux or tmux surface and arm a surface-aware watchdog (epic-mode drains). Use when the user runs `/drain-with-worker [cmux|tmux] DRAIN_ID` or accepts the `/drain` worker handoff. Takes an optional worker-type (auto-detected when omitted).

• draining-beads

  Use when you have an epic / set / cascade of beads to drain autonomously via Claude Code's /goal. Pairs with the /drain slash command. Requires Claude Code 2.1.148+ with hooks enabled.

• evolve-adr

  Use when you need to update, supersede, deprecate, or migrate an Architecture

• executing-plans

  Use when you have a written implementation plan to execute in a separate session with review checkpoints

• finishing-a-development-branch

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work (git or jj) - guides completion of development work by presenting structured options for merge, PR, or cleanup. Supports an autonomous (non-interactive) mode for callers like the drain worker that m

• handoff-prompt

  Generate a self-contained briefing prompt that a fresh Claude (or other agent) session uses to pick up a bead's work without inheriting the current session's context. Pulls model hint from the bead's `model:*` label (default sonnet), routes via the bead's `agent:*` label, and defers workspace setup

• plan-to-beads

  Materialize an implementation plan's task table into bd issues, dependency edges, and parent linkages per the design-bead lifecycle (Rule 6). Use after writing-plans + plan-reviewer return READY, after capture-adrs has fired, and before subagent-driven-development or executing-plans. Reads the plan'

• receiving-code-review

  Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

• requesting-code-review

  Use when completing tasks, implementing major features, or before merging to verify work meets requirements (supports git and jj) author: fzymgc-house

• respond-to-comments

  Manages GitHub PR review comments. Use when the user asks to "list PR comments", "check PR feedback", "respond to PR comments", "address reviewer feedback", "fix PR review issues", "work through PR review", or "acknowledge comments". Handles both quick lookups and full review-response workflows. - "

• review-pr

  Comprehensive PR review using specialized agents. Use when the user asks to "review this PR", "check my PR", "review code quality", "run PR review", "analyze this pull request", or invokes /review-pr. Launches targeted review agents for code quality, error handling, test coverage, type design, comme

• solving-a-bead

  Use when asked to solve, fix, address, or work a specific bead/issue by ID — validates the bead is open and unblocked, creates an isolated workspace off latest main, separates the problem from any suggested fix (treating suggested fixes as non-authoritative hypotheses), then drives a root-caused, TD

• subagent-driven-development

  Use when executing implementation plans with independent tasks in the current session

• systematic-debugging

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

• test-driven-development

  Use when implementing any feature or bugfix, before writing implementation code

• using-git-worktrees

  Alias for using-worktrees. Use when starting feature work that needs isolation from current workspace.

• using-superpowers

  Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

• using-worktrees

  Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git/jj fallback

• verification-before-completion

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

• writing-plans

  Use when you have a spec or requirements for a multi-step task, before touching code

• writing-skills

  Use when creating new skills, editing existing skills, or verifying skills work before deployment

• grepping

  Use when searching code or text from the shell with grep, egrep, fgrep, ugrep, ripgrep (rg), or ast-grep (sg) — especially when a search unexpectedly returns nothing, an rg flag errors (unrecognized flag, regex parse error, "missing value for flag -r"), or you are translating grep/BSD-grep muscle me

• miniflux

  Manage and curate a personal Miniflux RSS subscription set: feed management, reading & triage, AI curation, and health/maintenance. Wraps the official `miniflux` Python client via a uv-run gateway script (no MCP server required). Use when working with: (1) Feeds - subscribe/unsubscribe, organize int

• skill-qa

  Validates SKILL.md files against Claude Code skill best practices. Checks conciseness, description quality, progressive disclosure, workflow structure, and common anti-patterns. Use when reviewing or auditing skills before shipping. - Read - Grep - Glob author: fzymgc-house

• terraform

  Terraform Cloud operations and registry documentation lookup. Watch runs, view plan/apply logs, check workspace status, look up provider docs. Invokes Terraform MCP server on-demand without loading tool definitions into context. - "Bash(uv:*)" - "Bash(docker:*)" - "Bash(${CLAUDE_PLUGIN_ROOT}/skills/

• jujutsu

  Jujutsu (jj) VCS workflow guidance. MUST activate on ANY VCS operation when `jj root` succeeds or when `.jj/` exists in the repo root. Use when the user mentions jj, jujutsu, or when a colocated jj repo is detected. - "Bash(jj log)" - "Bash(jj log *)" - "Bash(jj diff *)" - "Bash(jj st)" - "Bash(jj s

• tmux

  tmux terminal-multiplexer usage. Use when spawning or driving tmux sessions/windows/panes from a script or agent, capturing pane output, targeting panes by id, or when the user mentions tmux. Covers detection, spawning, send-keys, capture-pane, and lifecycle.

MCP servers (1)

• terraform

  runs: docker run -i --rm -e TFE_TOKEN -e TFE_ADDRESS=https://app.terraform.io hashicorp/terraform-mcp-server:latest

Similar plugins