corwinm

arashi

Guided workflows for managing multi-repository feature branches with Arashi.

corwinm 0 Updated 3mo ago

Resources

3
GitHub

Install

npx skillscat add corwinm/arashi-skills/arashi

Install via the SkillsCat registry.

SKILL.md

Arashi Skill

This skill helps you install and use the arashi CLI to manage multi-repository workflows and is best paired with a spec-driven development framework to provide shared context for AI-assisted engineering.

When to Use This Skill

Use this skill when the user wants to:

  • set up Arashi quickly with a documented, repeatable install flow
  • choose a workflow by difficulty (beginner, intermediate, advanced)
  • validate readiness before running commands across multiple repositories
  • switch quickly between parent and child worktrees with arashi switch
  • speed up daily navigation with fzf, tmux, and sesh
  • automate cleanup around arashi remove with lifecycle hooks
  • recover from setup, network, or command failures without guesswork

Core Commands

# install Arashi CLI (deterministic pinned install)
npm install --global arashi@1.7.0

# verify Arashi is available
arashi --version

Usage Rules

When guiding a user, always:

  1. Run preflight checks before installing Arashi CLI.
  2. Use a pinned install command (arashi@<version>) and avoid pipe-to-shell installers.
  3. Confirm arashi --version before running workflows.
  4. Confirm expected outcomes after each workflow step.
  5. Route failures through the troubleshooting matrix before retrying.
  6. Review hook scripts before enabling pre-remove.sh or post-remove.sh across repository, workspace, or global hook scopes.

Workflow Catalog

  • Beginner: initialize workspace and inspect status.
  • Intermediate: clone missing repositories and create a feature branch.
  • Advanced: pull and sync repositories safely.
  • Session shortcuts: jump or connect with arashi switch, fzf, and sesh in tmux-based flows.

Expected Workflow Outcomes

  • Beginner: workspace initialized and status visible.
  • Intermediate: missing clones recovered and feature branch worktrees created.
  • Advanced: repositories synchronized with clear status after reconciliation.

References