me

Plugin me from marketplace bstack in baleen37/bstack. Commands read from the repo's manifest — 1 month ago.

Skills (10)

• browser

  Read when you need a browser automation (QA, element interaction, screencapture/snapshot, network capture, so on), or have to work across user's logged-in accounts, apps (e.g. Slack, X, LinkedIn, etc.), memory, and browsing history.

• code-review

  Review the current diff, or a PR number/branch/path target, for correctness bugs plus reuse/simplification/efficiency/altitude/conventions cleanups in one careful pass. Pass --comment to post findings as inline PR comments, or --fix to apply the findings to the working tree after the review. Use whe

• competitive-agents

  Use when designing systems, architectures, or APIs, when multiple valid approaches exist with no single obvious answer, or when user explicitly requests parallel/competing solutions

• create-pr

  Create PR — commit, push, PR, wait for merge.

• e2e-scenario-testing

  Use when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly built instance with falsifiable assertions. Trigger on "test it end to end", "prove the UI actually works", "write/run a

• learn

  Teach the user a new skill or concept over several sessions, in a workspace under `~/.bstack/learn/`.

• ship

  Use when preparing to deploy to production, asked to "ship", "release", or "deploy", or when you need to verify a deploy succeeded or plan a rollback. Covers the full flow: pre-deploy checks, the deploy itself, and post-deploy verification with rollback on failure.

• simplify

  Review the changed code for reuse, simplification, efficiency, and altitude cleanups, then apply the fixes. Quality only — it does not hunt for bugs; use me:code-review for that. Use when the user asks to simplify, clean up, or tidy the current diff without changing behavior.

• verify

  Verify that a code change actually does what it's supposed to by exercising it end-to-end and observing behavior — drive the affected flow, not just tests or typecheck. Run before committing nontrivial changes, or when asked to "verify this", "qa", or "does this work?"; bootstraps this repo's projec

• writing-rfcs

  Use when writing, reviewing, or improving RFCs, requests for comments, technical design docs, architecture proposals, engineering decision records, API proposals, migration plans, or cross-team technical decisions.

Subagents (1)

• researcher

  Use this agent to find and verify external reference material from official documentation, APIs, registries, standards, papers, releases, GitHub sources, and reputable web sources. Do not use for codebase exploration or local bug investigation.

Hooks (7)

• WorktreeCreate

  bash "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/setup-worktree.sh"

• PreToolUse

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/commit-guard.sh"

• SessionStart

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/agent-status.sh"

• UserPromptSubmit

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/agent-status.sh"

• PermissionRequest

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/agent-status.sh"

• Stop

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/agent-status.sh"

• SessionEnd

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/agent-status.sh"

Similar plugins