sst

Plugin sst from marketplace sst-claude-marketplace in shanethacker/sst-claude-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (7)

• explain-code

  Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?

• explain-pr

  Produce a comprehensive markdown document explaining all changes in a pull request, branch, or commit range — covering the architecture involved, what each change does and why, and how the pieces fit together. Use this skill whenever the user asks to "explain this PR", "walk me through these changes

• gen-test

  This skill should be used when the user asks to "generate tests", "write tests for", "add test coverage", "create unit tests", "write a test file", or "add tests to". Generates tests that match the project's established conventions by discovering patterns from existing tests before writing anything

• make-presentation

  This skill should be used when the user asks to "create a presentation", "build a deck", "make a tech talk", "draft slides on X", "write a presentation about", or wants to develop technical presentation content iteratively — architecture/coding decisions for peer developers, security or technical pl

• pr-check

  This skill should be used when the user asks to "run pre-PR checks", "check before pushing", "run quality checks", "verify the branch is ready", "run lint and tests", or "make sure CI will pass". Runs the project's quality gates locally to catch failures before they hit the pipeline.

• review-dependabot-prs

  This skill should be used when the user mentions "dependabot", "dependency updates", "review dependency PRs", "check dependabot PRs", or asks about open PRs from Dependabot. Reviews open Dependabot pull requests for compatibility, urgency, breaking changes, and CI/CD status, producing a structured r

• update-runbooks

  This skill should be used when the user asks to "update runbooks", "audit runbooks", "check if runbooks are accurate", "verify operational docs", "runbook drift", or "sync runbooks with the code". Verifies that operational runbooks reflect the current state of the codebase and updates anything that

Subagents (3)

• code-reviewer

  Use this agent when a meaningful chunk of code has been written or modified and needs review for quality, conventions, and correctness — especially after completing a feature, fixing a bug, or finishing a logical implementation step. Examples: <example> Context: The user has just implemented a new A

• presentation-reviewer

  Use this agent when a technical presentation draft (a markdown deck produced by the make-presentation skill) needs review for structure, clarity, and accessibility — specifically after a draft or revision pass, before the presenter iterates further or exports to slides. Examples: <example> Context:

• security-reviewer

  Use this agent when code changes need a security review — before opening a PR on security-sensitive changes, after implementing authentication or authorization features, when adding external API integrations, or when handling user input, file uploads, or sensitive data. Examples: <example> Context:

Similar plugins