brane-impact

Analyze Brane SDK code changes to identify affected modules and tests.

9|1|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/noise-xyz/brane --skill brane-impact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brane-impact
Source: https://github.com/noise-xyz/brane/tree/main/.claude/skills/brane-impact
Command: npx skills add https://github.com/noise-xyz/brane --skill brane-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brane Impact helps development teams understand the ripple effects of code changes in the Brane SDK by surfacing which modules and tests may be affected and guiding safe test planning.

Core Features & Use Cases

  • Impact propagation across primitives, core, rpc, contract, and consumer modules to surface downstream effects.
  • LSP-based impact analysis to precisely locate usages and definitions across the codebase.
  • Fallback test discovery methods and module-specific test commands to quickly locate relevant tests and plan validation.

Quick Start

Identify changed files with git diff, then run the automated impact analysis to generate reports and recommendations. Use the module-specific test commands to execute unit, integration, and smoke tests for affected areas.

Frequently Asked Questions about brane-impact

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

FAQPage Schema
How do I analyze code changes to find affected modules and tests?

Impact analysis uses LSP-based references to trace code changes across primitives, core, rpc, contract, and consumer modules. It locates definitions and usages to precisely map downstream effects and identify which tests are affected.

How do I discover and run unit and integration tests after modifying an SDK?

You discover and run tests after modifying an SDK by using fallback test discovery methods and module-specific test commands. This guides execution of unit, integration, and smoke tests to validate affected areas and ensure safe changes.

What is LSP-based impact analysis and when do I need it for test discovery?

LSP-based impact analysis is a method that uses Language Server Protocol references to precisely locate usages and definitions across a codebase. You need it to map ripple effects and discover relevant tests when modifying complex module layers.

Can I assess risk for changes across core, rpc, and contract layers?

Yes, you can assess risk for changes across core, rpc, and contract layers. The impact analysis propagates changes from primitives through consumer modules, surfacing downstream effects and providing end-to-end testing guidance for safe validation.

What is the best way to map downstream effects when updating shared primitives?

The best way to map downstream effects when updating shared primitives is to run automated impact propagation. It traces references through core, rpc, and consumer modules to generate risk assessment reports and recommend targeted tests.