base

Plugin base from marketplace my-marketplace in kkhys/claude-code-marketplace. Commands read from the repo's manifest — yesterday.

Skills (29)

• babysitting-pr

  Monitor a pull request until it is genuinely mergeable — long-poll CI checks, review threads, and merge state; fix branch-caused CI failures and actionable review comments autonomously; re-request Copilot review after every fix round until Copilot stops commenting. Trigger whenever the user wants a

• cleaning-workspace

  Delete every local branch of the current repository except the protected ones, after showing the list once

• creating-branch-name

  Create a git branch with an appropriate name derived from current changes, following the <type>/<description> convention.

• creating-handoff

  Compact the current conversation into a handoff document — a file under ~/.claude/handoffs/, or appended to a Notion page — so a fresh session can continue the work

• creating-pr

  Create GitHub pull requests following required project conventions: title format "[base-branch] type: description", mandatory --draft flag, and --assignee kkhys.

• creating-stacked-pr

  Decide whether a development task should be a stack of dependent PRs — single PR is the default answer — design the layers at reviewable granularity, and build the stack with the gh-stack CLI under this project's conventions ("[main] type: description" titles, draft PRs, assignee kkhys). Always cons

• diagnosing-bugs

  Six-phase discipline for a hard bug or performance regression — build a red-capable feedback loop, reproduce and minimise, rank hypotheses, instrument, fix behind a regression test, clean up

• diagnosing-ci-failure

  Diagnose one failed CI run or a PR's failing checks from a URL: pull the failed job logs, name the cause with the log excerpt, classify it as branch-caused or flaky, then fix it on the PR branch as a new commit or rerun the failed jobs. Use when the user pastes a GitHub Actions run URL or a PR URL w

• digging

  Interrogate a plan, design, or technical decision one question at a time until shared understanding is reached

• drafting-message

  Draft a short Japanese message the user will post themselves — a Slack reply or share, a request to QA / design / support / another team, a Notion or PR comment — sized and worded for the named audience, shown in chat, and copied to the clipboard. Never posts anything. Use whenever the user wants te

• eli15

  Explain a topic the user names from zero as a one-page HTML picture explainer — drawn pictures, few plain words, pitched at a smart fifteen-year-old

• explaining-like-doraemon

  Re-explain a difficult answer as a Doraemon-Nobita dialogue, then restate it in precise terms

• fixing-review-comments

  Address unresolved review comments on the current branch by orchestrating the full fix cycle: reading feedback, implementing changes, verifying, committing, and replying to reviewers. Trigger whenever the user wants to fix PR review feedback, address reviewer comments, handle review points, or respo

• formatting-commit

  Enforce Conventional Commits format for git commits, including project-specific scope conventions (plugin name as scope in this marketplace) and the new-commit-versus-amend decision — new commit by default, always under review.

• illustrating-pr

  Draw a pull request as one eli15 picture for an engineer reader and place it in the PR description (or a comment) with gh --attach

• managing-devin-automations

  Create, inspect, edit, disable, or delete a Devin automation through the v3 API, and write the prompt or Devin skill it runs. - Bash(bash:*) - Bash(jq:*) - Read - Write

• merging-renovate-prs

  Merge the open Renovate pull requests of a repository owned by kkhys, one at a time — squash on green CI, wait for Renovate's own rebase when a PR falls behind, diagnose and fix a check the bump broke, and report what stays blocked. Refuses any repository whose owner is not kkhys and never touches a

• posting-pr-review

  Post review comments to a GitHub PR as a PENDING review using the post-pr-review.sh workflow script — severity-tagged ([critical]/[warning]/[question]/[suggestion]), one or two lines each, substantive findings only.

• publishing-pr

  Complete git workflow — create branch, split commits, and create PR

• reading-unresolved-pr-comments

  Fetch and analyze unresolved PR review comments using a specialized GraphQL script that extracts thread-level data (thread IDs, resolution status, outdated flags, line ranges) not available through basic gh commands, then produce a fix plan. MUST consult whenever the user wants to check review feedb

• recording-pr-qa

  Run a PR's manual test in a headless browser, capture each case as a screenshot or a captioned video with an in-video console, and place the evidence with the case list in the PR description — in the repository's template sections when it has them — or, on a PR the user reviews, in their pending rev

• recording-qase-qa

  Run a PR's manual test against its Qase cases — record them into the QA run with a clip per case, create the missing cases, and turn the repeatable ones into a Playwright spec on a stacked PR

• registering-hex-vocabulary

  Teach Hex (dictation) the product, project, and tool names in the prompts typed into Claude Code since the last run, each with the spellings a Japanese transcript shows for it, and turn the mishearings in Hex's own dictation history — a wrong kanji, a split name, a stock closing line — into replacem

• resolving-merge-conflicts

  Resolve an in-progress git merge, rebase, or cherry-pick conflict by intent: trace each side to its primary source (commit, PR, issue), preserve both intents per hunk, run the project's own checks, and carry the operation to a finished commit. A PR into develop that GitHub reports as conflicting is

• resolving-pr-comments

  Resolve review threads on the current PR via the GraphQL API — every unresolved thread after confirming with the user, or a specific list of thread IDs when a calling workflow supplies them. Use when the user wants to bulk-resolve PR comments after addressing feedback, mark threads as done, or close

• reviewing-pr

  Review a pull request, or a whole stacked series, and close with a fixed verdict block: approve or not, reproducible bugs with steps a human can run, findings with nits stripped, regression and feature-flag scope risk, and a one-line manual test checklist. Delegates the review itself to pr-review-to

• splitting-commit

  Split large uncommitted changes into logical commits by semantic concern, producing a reviewable, bisectable history.

• writing-for-agents

  Levers for writing any document an agent consumes — a skill, CLAUDE.md / AGENTS.md, an agent definition, a reference reached by a pointer: context pointers, the two loads, information hierarchy, completion criteria, leading words, pruning. Always consult before creating or editing a SKILL.md, CLAUDE

• writing-qase-cases

  Rules for what a Qase test case holds: only what lasts as long as the behaviour, variants as parameters (single, group, shared), and where the PR, the ticket, a feature flag and the environment go instead. Always consult before creating or editing a Qase test case, through the API or a Qase MCP tool

MCP servers (1)

• serena

  runs: uvx --from git+https://github.com/oraios/[email protected] serena start-mcp-server

Hooks (1)

• Stop

  ${CLAUDE_PLUGIN_ROOT}/scripts/cleanup-merged-branches.sh

Similar plugins