Stats
Links
Categories
Help us improve
Share bugs, ideas, or general feedback.
Claude Code plugins for GitHub driven code development workflow
npx claudepluginhub hhiroshell/gh-devflow-pluginsPlan and implement GitHub issues with structured workflows for issue-driven development
Open Design — local-first design app exposed to coding agents over MCP. Install once with your agent's plugin command and projects/files/skills are reachable through stdio.
Claude Code plugins for the Slidev presentation framework
Bundled plugins for actuating and debugging the Chrome browser.
Share bugs, ideas, or general feedback.
A collection of Claude Code plugins for GitHub driven code development workflow.
This repository contains plugins designed to streamline development workflows that center around GitHub Issues and Pull Requests. These plugins help bridge the gap between issue tracking and implementation by automating planning, documentation, and code review processes.
| Plugin | Description |
|---|---|
| github-devflow | Plan and implement GitHub issues with structured workflows for issue-driven development |
To use these plugins with Claude Code, add this repository as a plugin marketplace.
From within Claude Code, run:
/plugin marketplace add hhiroshell/gh-devflow-plugins
Then install the plugin from the marketplace:
/plugin install github-devflow@gh-devflow-plugins
/github-devflow:plan <issue-number>Analyzes a GitHub issue and the codebase to generate a structured implementation plan. The plan includes affected files, step-by-step implementation guidance, testing approach, and potential risks. The plan is automatically posted as a comment on the issue for review.
/github-devflow:implement <issue-number>Implements a GitHub issue by reading the implementation plan from the issue comments, writing the code, and creating a pull request. Automatically links the PR to the issue and adds appropriate labels.
/github-devflow:code-review <pr-number>Performs a comprehensive multi-perspective code review of a pull request. Dispatches 8 specialized reviewer agents in parallel (logic, design, security, performance, convention compliance, git history, PR history, documentation), each analyzing with a clean context. Aggregates all findings into a single GitHub PR review with line-specific comments and a summary.
/github-devflow:reply <pr-number>Replies to unresolved review threads on a pull request. Fetches threads where the latest comment was not generated by Claude Code, analyzes comments with full codebase context, and posts thoughtful replies addressing reviewer concerns.
/github-devflow:fix <pr-number>Processes unresolved PR review threads by autonomously deciding and executing the appropriate action for each: fixing the code (with auto-commit), creating a GitHub issue for out-of-scope problems, or dismissing minor suggestions. Replies to each thread reporting the action taken, then pushes all commits.
/github-devflow:plan <number> to analyze an issue and generate an implementation plan/github-devflow:implement <number> to implement the plan and create a PR/github-devflow:code-review <pr-number> to get a multi-perspective code review/github-devflow:reply <pr-number> to respond to PR review comments/github-devflow:fix <pr-number> to fix code, create issues, or dismiss review commentsgh) installed and authenticatedGitHub driven development treats GitHub Issues as the source of truth for requirements and Pull Requests as the primary unit of work. These plugins support this workflow by:
Releases are automated via GitHub Actions. Claude Code uses plugin.json version as a cache key, so each release must have a unique version and main must always differ from any released version.
github-devflow/.claude-plugin/plugin.json — authoritative version (cache key). Set to X.Y.Z on release tags, X.(Y+1).0-dev on main between releases..claude-plugin/marketplace.json — ref-based source pinned to the latest release tag (e.g., v0.5.0)../scripts/release.sh <version> (e.g., ./scripts/release.sh 0.5.0)
plugin.json version to 0.5.0 and marketplace.json ref to v0.5.0v0.5.0plugin.json to 0.6.0-dev, commitsmain and the tagplugin.json version matches the tag and marketplace.json ref matches the tag name, then creates a GitHub Release with auto-generated notesMIT