devkit

devkit

A Claude Code plugin with debugging, code analysis, and developer productivity commands.

Install

Run these commands in your terminal:

claude plugin marketplace add shiyas1331/devkit
claude plugin install devkit@shiyas-devkit

Restart your Claude Code session. The plugin is now available.

From Source (local testing)

If you want to make changes and test locally:

git clone https://github.com/shiyas1331/devkit.git
cd devkit
claude --plugin-dir .

Upgrade

When a new version is released:

claude plugin marketplace update shiyas-devkit
claude plugin update devkit@shiyas-devkit

Changes take effect in your next Claude Code session.

Uninstall

claude plugin uninstall devkit@shiyas-devkit
claude plugin marketplace remove shiyas-devkit

Commands

/devkit:why — Why does this code exist?

Replaces the daily 5-minute git blame + GitHub-clicking dance with a 10-second answer. Tells you who added the code, when, in which PR, with what reasoning. Pulls blame, originating commit, PR description, linked JIRA ticket, and review-thread highlights into one grounded explanation.

Walks line history. The most recent commit on a line is often a typo fix or formatter run — not the answer to "why." This command walks back through history (skipping trivial commits like typo/format/lint/rename/bot edits) to find the substantive originator. The walk count is shown so you know how far it traced.

Usage:

/devkit:why packages/editors/src/api/apiClient.ts:188
/devkit:why apiClient.ts                          # entire file's origin
/devkit:why apiClient.ts:120-150                  # block of lines
/devkit:why apiClient.ts:188 --depth=thorough     # full drilldown
/devkit:why apiClient.ts:188 --max-walk=10        # walk further back
/devkit:why apiClient.ts:188 --json               # machine-readable output

Detects special cases:

• Trivial commits (typo, format, lint, rename) — skipped during the walk
• Code that was added then reverted later
• Code superseded by a follow-up PR
• Lines moved from another file (with rename history via git log --follow)
• Squash merges (authoritative detection via PR merge_method)
• Direct pushes to main with no PR
• Generated/vendored files (path + content sniffing)
• Working-tree drift (target line has unstaged changes)
• Submodule paths (auto-descends)

Mechanical confidence labels (no judgment-call variance):

• high — PR body or commit message explicitly explains the why (because, to fix, to address, etc.). OR ticket description >100 chars.
• medium — Linked ticket has meaningful title. OR review thread has ≥2 rationale comments. OR commit body >100 chars.
• low — Only commit subject available, or --max-walk cap was hit.
• none — Direct push, one-line subject, no recoverable why.

Configurable ticket prefixes via TICKET_PREFIXES env var (e.g., TICKET_PREFIXES=CAT,COVEX) to prevent ghost tickets from over-permissive regex.

Used internally by /devkit:pr-review for "why" inferences — this command is the single source of truth for git archaeology.

/devkit:address-pr — Address PR review feedback efficiently

Author-side companion to /devkit:pr-review. Reads open reviewer comments, classifies them, drafts code fixes for change-requests and replies for questions, commits in smart batches, posts replies, resolves threads, and re-requests review — all with explicit author approval at every step.

Usage:

/devkit:address-pr 409
/devkit:address-pr 409 --dry-run                 # show plan only, no changes
/devkit:address-pr 409 --ignore-bots             # skip CodeRabbit / dependabot etc.
/devkit:address-pr 409 --reviewer=senior-rev     # only this reviewer's comments
/devkit:address-pr 409 --auto-resolve            # mark threads resolved after fixes land

Comment classification:

Type	Action
change-request	Draft code fix; ask before applying
nit	Batch with other nits in the same file → one commit
question	Draft reply; queue for batch posting
suggestion	Draft both a fix proposal and a discussion reply
praise	Acknowledge in summary, no action
out-of-scope	Reply acknowledging deferral; do not auto-resolve
stale	Detect line already changed; suggest resolving without code change
conflict	Surface to author when two reviewers ask for opposing changes — never silently picks one

Smart features:

• Plan before action — full preview, then per-item confirmation
• Push-back drafting — when the author disagrees, helps draft a respectful counter-argument
• Smart commit grouping — nits in same file batched, substantive changes individual
• Stale-comment detection — won't waste time on already-fixed concerns
• Resume from interruption — never starts from scratch on re-run

The author stays in control. Nothing is committed or posted without explicit confirmation.