Skip to content

feat: register Ripple in community catalog#2272

Open
chordpli wants to merge 3 commits intogithub:mainfrom
chordpli:feat/add-ripple-extension
Open

feat: register Ripple in community catalog#2272
chordpli wants to merge 3 commits intogithub:mainfrom
chordpli:feat/add-ripple-extension

Conversation

@chordpli
Copy link
Copy Markdown
Contributor

Extension Submission

Extension Name: Ripple
Extension ID: ripple
Version: 1.0.0
Author: chordpli
Repository: https://github.com/chordpli/spec-kit-ripple

Motivation

After implementation, tests verify intended behavior — but they're rarely designed to detect what a change does to code outside the change set. Ripple was created to address this gap: detecting side effects caused by changes you just made, within the scope of those changes.

How It Differs from Existing Extensions

Code Review (review, staff-review) Ripple
Analyzes The changed code itself The impact on code that wasn't changed
Asks "Is this code good?" "What did this change break elsewhere?"
Baseline None — evaluates code as-is git merge-base — compares before/after
Pre-existing issues Reports them Excludes them (causation test)
Best used Together — review catches code quality, Ripple catches ripple effects

How It Works

scan compares the implementation against the baseline (git merge-base) and analyzes across 9 domain-agnostic categories (Data Flow, State & Lifecycle, Interface Contract, Resource & Performance, Concurrency, Distributed Coordination, Configuration & Environment, Error Propagation, Observability). Every finding must pass a causation test: "If this implementation had not been made, would this problem exist?" If yes, it's a pre-existing issue and excluded from the report.

resolve was inspired by /speckit.clarify. Each side effect can be fixed in multiple ways with different tradeoffs. For each finding, it presents 2-4 concrete fix strategies (e.g., minimal patch, structural refactor, defer to next release) and asks: "How do you want to fix this, and what outcome do you expect?" Decisions are recorded in ripple-report.md and implementation guidance is saved to ripple-fixes.md — ready for /speckit.implement to consume.

check re-verifies findings after fixes are applied and detects fix-induced side effects — new problems created by the fixes themselves. This creates a feedback loop: fixes may introduce new risks, which check catches before the next iteration. Real-world testing showed convergence from 3 CRITICAL → 1 CRITICAL → 0 CRITICAL, with each check cycle surfacing issues introduced by previous fixes.

Hook: after_implement — prompts to scan after implementation completes.

Checklist

  • Valid extension.yml manifest
  • README.md with installation and usage docs
  • LICENSE file included
  • GitHub release created (v1.0.0)
  • Extension tested on real project
  • All commands working
  • No security vulnerabilities
  • Added to extensions/catalog.community.json
  • Added to Community Extensions table in README.md

Testing

  • macOS 14.5, spec-kit 0.7.2
  • 3 full scan cycles completed with fix-induced detection verified

- Extension ID: ripple
- Version: 1.0.0
- Author: chordpli
- 3 commands (scan, resolve, check), 1 hook (after_implement)
- Delta-anchored side effect detection across 9 domain-agnostic categories
@chordpli chordpli requested a review from mnriem as a code owner April 19, 2026 14:08
Copilot AI review requested due to automatic review settings April 19, 2026 14:08
@chordpli chordpli changed the title Add Ripple extension to community catalog feat: register Ripple in community catalog Apr 19, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds the Ripple community extension to Spec Kit’s community catalog and surfaces it in the main README’s Community Extensions table.

Changes:

  • Bumps the community catalog’s top-level updated_at timestamp.
  • Adds a new ripple entry to extensions/catalog.community.json with metadata (download URL, docs, tags, requirements, etc.).
  • Adds a corresponding “Ripple” row to the Community Extensions table in README.md.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
extensions/catalog.community.json Adds the Ripple extension entry and updates the catalog timestamp.
README.md Adds Ripple to the Community Extensions table.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread extensions/catalog.community.json Outdated
Moved ripple catalog entry from between reconcile/refine to between
review/security-review. Updated README table order to match.
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread extensions/catalog.community.json Outdated
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants