Overview

add-sub lets you subscribe to a skill event and inject context before or after a skill runs. It supports insert-level conditions that apply to all subscriptions and subscription-level conditions that are AND-stacked. Supported conditions include fileExists, gitBranch, envSet, envEquals, and fileContains (with optional regex).

How This Skill Works

The skill delegates to the /skill-bus:add-sub command for the full interactive process. Run the command directly to start the subscription flow. Insert-level conditions apply to every subscription, while subscription-level conditions are evaluated in an AND fashion for each entry.

When to Use It

• Need context injected only when working on a specific git branch.
• When a required config file exists and should influence skill behavior.
• To set environment variables before a skill executes.
• When you want to conditionally apply after-skill context based on file contents.
• To guard subscriptions with regex-enabled fileContains checks.

Quick Start

1. Step 1: Run /skill-bus:add-sub to open the interactive setup.
2. Step 2: Choose before or after, select the skill events, and specify insert-level conditions.
3. Step 3: Add one or more subscriptions with their own conditions and save.

Best Practices

• Define clear insert-level conditions to cover all subscriptions.
• Keep subscription-level conditions specific to each subscription to avoid unintended matches.
• Test conditions on representative scenarios (branch, files, env).
• Document the subscription rules and version them.
• Avoid heavy or slow checks in fileContains regex; use simple patterns.

Example Use Cases

• Inject a user role or tenant ID before user-facing skills run.
• Only on main/master branch when a config exists, inject global settings.
• Set API keys in envSet before relevant skills execute.
• Add context after a report-generating skill to enrich logs.
• Trigger on a regex in config fileContains to adjust behavior.

Frequently Asked Questions