monitor-version
Bumps the version header in pipeline-monitor.sh automatically.
Install
mkdir -p .claude/skills/monitor-version && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13057" && unzip -o skill.zip -d .claude/skills/monitor-version && rm skill.zipInstalls to .claude/skills/monitor-version
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Auto-bump pipeline monitor version when builder/monitor/pipeline-monitor.sh is modified. Triggers automatically as a post-edit convention — not user-invocable directly. When any change is made to pipeline-monitor.sh, increment the patch version in the "# Version:" header comment. Triggers on: "pipeline-monitor", "monitor version", "bump monitor".Key capabilities
- →Read the current version from the `# Version:` line.
- →Determine bump type based on the nature of the change.
- →Update the `# Version:` line with the new version.
- →Increment patch version for bug fixes, minor tweaks, style changes.
- →Increment minor version for new features.
- →Increment major version for breaking changes.
How it works
The skill reads the current version from a specific line in `pipeline-monitor.sh`, determines the appropriate semantic version bump based on the change type, and updates the version line.
Inputs & outputs
When to use monitor-version
- →Bump monitor version
- →Auto-update version header
About this skill
Monitor Version Bump
Automatically increment the version in builder/monitor/pipeline-monitor.sh whenever the file is modified.
Convention
The version lives on line 4 of builder/monitor/pipeline-monitor.sh in the format:
# Version: X.Y.Z
Versioning rules
- Patch (0.6.0 → 0.6.1): bug fixes, minor tweaks, style changes
- Minor (0.6.1 → 0.7.0): new features (new key binding, new tab, new view mode)
- Major (0.7.0 → 1.0.0): breaking changes to keyboard shortcuts or tab layout
Workflow
When modifying builder/monitor/pipeline-monitor.sh:
- Read the current version from the
# Version:line (line 4) - Determine bump type based on the nature of the change:
- Bug fix / refactor / cosmetic → patch bump
- New feature (key, tab, view, action) → minor bump
- Breaking change to existing behavior → major bump
- Update the
# Version:line with the new version - This step should be done as part of the same edit — not as a separate commit
Example
Before (bug fix to log rendering):
# Version: 0.6.0
After:
# Version: 0.6.1
Before (added [l] key for task logs):
# Version: 0.5.0
After:
# Version: 0.6.0
When not to use it
- →When the `builder/monitor/pipeline-monitor.sh` file is not modified.
- →When the versioning rules are not applicable.
- →When a separate commit is desired for the version bump.
Limitations
- →It is not user-invocable directly.
- →It triggers automatically as a post-edit convention.
- →The version lives on line 4 of `builder/monitor/pipeline-monitor.sh`.
How it compares
This skill automates the semantic version bumping of a specific script based on predefined rules, ensuring consistent versioning without manual intervention, unlike manually updating the version number.
Compared to similar skills
monitor-version side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| monitor-version (this skill) | 0 | 4mo | No flags | Beginner |
| session-status | 1 | 7mo | Review | Beginner |
| it-operations | 1 | 7mo | No flags | Advanced |
| customerio-cost-tuning | 0 | 27d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
session-status
WellApp-ai
Generate breadcrumb headers/footers with takt time tracking and muda metrics
it-operations
davila7
Manages IT infrastructure, monitoring, incident response, and service reliability. Provides frameworks for ITIL service management, observability strategies, automation, backup/recovery, capacity planning, and operational excellence practices.
customerio-cost-tuning
jeremylongshore
Optimize Customer.io costs and usage. Use when reducing expenses, optimizing usage, or right-sizing your Customer.io plan. Trigger with phrases like "customer.io cost", "reduce customer.io spend", "customer.io billing", "customer.io pricing".
perplexity-incident-runbook
jeremylongshore
Execute Perplexity incident response procedures with triage, mitigation, and postmortem. Use when responding to Perplexity-related outages, investigating errors, or running post-incident reviews for Perplexity integration failures. Trigger with phrases like "perplexity incident", "perplexity outage", "perplexity down", "perplexity on-call", "perplexity emergency", "perplexity broken".
plex
Akpo-Fure
>-
oly
slaveOftime
Use when starting a long-running or interactive CLI command with oly, especially when it may need later input, should be detachable, or should keep durable logs for supervision and resume.