stacklane

stacklane

Operational plugin for script-backed execution workflows.

Default profile:

• runtime: bun
• frontend: nextjs
• database: supabase
• deploy: railway

You can override adapters (for example frontend=tanstack, deploy=flyio) via .stacklane.json or /stacklane:init flags.

stacklane is execution-focused. Use plangate for process/governance (plan -> implement -> gate -> review).

Installation

/plugin marketplace add bishnubista/stacklane
/plugin install stacklane@stacklane

What Makes This Useful

Every /stacklane:* command delegates to deterministic scripts in scripts/:

• strict argument parsing
• production confirmation token enforcement
• release/migration/incident artifact writing
• profile + command templates from .stacklane.json
• rollback checkpoints and verification

This avoids ad-hoc prompt behavior for critical production actions.

Niche focus:

• Bun app operations with Supabase migrations and Railway/Fly deployment control
• explicit safety over broad platform coverage

Supported Adapters

Dimension	Supported values
runtime	bun
frontend	nextjs, tanstack, none
database	supabase, none
deploy	railway, flyio, none

Notes:

• migrate-safe currently requires database=supabase.
• deploy-verify and incident require deploy != none.
• Railway rollback is intentionally not auto-defined; configure commands.rollback for your service.

Prerequisites

• Claude Code
• Git repository
• Bun CLI
• Supabase CLI (if database=supabase)
• Railway CLI (if deploy=railway)
• Fly CLI (if deploy=flyio)

Commands

Command	Script entrypoint	Purpose
/stacklane:init	scripts/stacklane-init.sh	Baseline setup, profile/config scaffolding, runbook, validation
/stacklane:migrate-safe	scripts/stacklane-migrate-safe.sh	Migration safety checks, rollback notes, apply report
/stacklane:deploy-verify	scripts/stacklane-deploy-verify.sh	Preflight, deploy, verify, and optional rollback
/stacklane:incident	scripts/stacklane-incident.sh	Incident logging, evidence capture, rollback mitigation

Production Safety Gate

For production migration/deploy/rollback, scripts require:

--confirm-production I_UNDERSTAND_PRODUCTION

If omitted, execution is blocked.

Stack Detection

Session-start hook emits <stacklane-manifest> with:

• active profile
• adapter readiness (runtime/frontend/database/deploy)
• raw markers (Next.js/TanStack/Supabase/Railway/Fly)
• resolved command templates

.stacklane.json Configuration

Created by scripts/stacklane-init.sh if missing.

{
  "profile": {
    "runtime": "bun",
    "frontend": "nextjs",
    "database": "supabase",
    "deploy": "railway"
  },
  "defaults": {
    "environment": "staging",
    "service": "web"
  },
  "healthcheck": {
    "url": "",
    "timeoutSeconds": "60",
    "intervalSeconds": "5"
  },
  "adapters": {
    "database": {
      "migrationsDir": "supabase/migrations"
    }
  },
  "commands": {
    "install": "bun install",
    "typecheck": "bunx tsc --noEmit",
    "lint": "bunx next lint",
    "test": "bun test",
    "build": "bun run build",
    "migrateLint": "supabase db lint",
    "migrateApply": "supabase db push",
    "deploy": "railway up --detach --service {service} --environment {environment} --message stacklane:{release_id}",
    "currentRelease": "railway deployment list --service {service} --environment {environment} --limit 10 --json",
    "rollback": "",
    "logs": "railway logs --service {service} --environment {environment} --lines 200",
    "smoke": ""
  }
}

Template variables available inside command strings:

• {service}
• {environment}
• {release_id}
• {rollback_target}
• {deployment_id}

Notes:

• healthcheck.url must be an absolute http:// or https:// URL.
• For Fly.io, default rollback template is fly releases rollback {rollback_target} --app {service} --yes.

/stacklane:init Profile Flags

scripts/stacklane-init.sh \
  --frontend tanstack \
  --deploy flyio \
  --service my-fly-app \
  --healthcheck-url https://example.com/healthz

Artifacts

Execution writes operational records to .stacklane/:

• .stacklane/init-report.md
• .stacklane/migration-reports/*
• .stacklane/releases/*
• .stacklane/incidents/*
• .stacklane/state/*

Verification

./try-stacklane.sh
./try-stacklane.sh --scaffold
claude plugin validate .

Boundaries

stacklane intentionally does not provide:

• planning/governance orchestration (use plangate)
• broad generic helper commands duplicated by official plugins

Support

• Issues: https://github.com/bishnubista/stacklane/issues
• Contact: collab@bishnu.dev

License

MIT