brane-ship

Automate verify-to-commit workflows for Brane SDK changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end workflow for verifying and committing Brane SDK changes. It ensures that changes are analyzed for impact, tested across affected modules in dependency order, and prepared for safe commit and push.

Core Features & Use Cases

  • Impact analysis using the brane-impact logic to identify affected modules and dependencies.
  • Sequential, multi-layer testing (unit, integration, and smoke) across affected modules.
  • Pre-commit checks and commit/push with conventional messages.

Quick Start

Invoke /brane-ship after implementing a fix or feature to trigger the complete verification-to-commit workflow.

Frequently Asked Questions about brane-ship

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

FAQPage Schema
How do I verify and commit multi-module SDK changes safely?

To verify and commit multi-module SDK changes safely, you can automate the workflow to detect changes, run impact analysis, execute sequential tests, and push commits with conventional messages.

What is impact analysis for multi-module testing workflows?

Impact analysis for multi-module testing identifies affected modules and dependencies, ensuring sequential unit, integration, and smoke tests run in the correct dependency order before committing changes.

How do I automate pre-commit checks and conventional commit messages?

You can automate pre-commit checks and conventional commit messages by orchestrating a workflow that executes verification checks and generates commit messages formatted with conventional standards.

Does this verification workflow support unit, integration, and smoke testing?

Yes, this verification workflow supports sequential multi-layer testing across affected modules, orchestrating unit, integration, and smoke tests before reaching a ready-to-commit state.

When do I need automated impact analysis for SDK commits?

You need automated impact analysis for SDK commits when your code changes touch multiple modules, requiring comprehensive dependency evaluation and multi-layer testing to ensure safe integration.