plugin-dev-workflow

Guide plugin development workflow for the Claude Ruby/Grape repository.

7|Updated Mar 22, 2026

Search Tags:#workflow #development #validation #claude #plugin #ruby #grape

Ready to run

npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill plugin-dev-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-dev-workflow
Source: https://github.com/slbug/claude-ruby-grape-rails/tree/main/.claude/skills/plugin-dev-workflow
Command: npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill plugin-dev-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It provides a clear, step‑by‑step guide for contributors to safely modify either the shipped Ruby/Grape plugin code or the internal Claude tooling, preventing accidental cross‑contamination and ensuring release‑ready changes.

Core Features & Use Cases

Surface separation: distinguishes between shipped plugin files and contributor‑only tooling.
Validation matrix: runs appropriate linters, shellcheck, Ruby syntax checks, and plugin validators based on changed files.
Release discipline: automates version bump coordination, changelog updates, and documentation sync.
Audit & roadmap maintenance: keeps planning notes and recommendations aligned with the current codebase.

Quick Start

Invoke the workflow by running /rb:plan <feature description> in your terminal.

Frequently Asked Questions about plugin-dev-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate changes to a Ruby Grape plugin before submitting?▼

To validate Ruby Grape plugin changes, run the appropriate linters, shellcheck, Ruby syntax checks, and plugin validators based on the specific files you modified within the repository.

What is the correct workflow for modifying shipped Claude plugin code?▼

The correct workflow for modifying shipped Claude plugin code involves distinguishing between shipped files and contributor tooling, running validation matrices, and coordinating version bumps to prevent cross-contamination.

How do I coordinate version bumps and changelog updates for Claude plugin releases?▼

Coordinate version bumps and changelog updates for Claude plugin releases by applying release discipline automation that synchronizes documentation and aligns planning notes with the current codebase.

Can I use this workflow to update contributor tooling separately from shipped Ruby plugins?▼

Yes, you can update contributor tooling separately from shipped Ruby plugins because the workflow enforces surface separation to prevent accidental cross-contamination between internal tooling and release-ready code.

What's the best way to start planning a feature for a Claude Ruby Grape repository?▼

The best way to start planning a feature for a Claude Ruby Grape repository is invoking the workflow via terminal using the command `/rb:plan <feature description>` to guide development steps.

Why do I need validation steps when developing Claude Ruby plugins?▼

You need validation steps when developing Claude Ruby plugins to ensure release-ready changes, maintain version alignment, and follow release discipline without requiring manual oversight during modifications.