skill tag

DevOps Community

Skill notes

Command Syntax

Flag · Description --patch · Increment patch version (default): v0.2.3 -> v0.2.4 --minor · Increment minor version, reset patch: v0.2.3 -> v0.3.0 --major · Increment major version, reset minor and patch: v0.2.3 -> v1.0.0 --force · Skip confirmation prompt

Step 1: Parse Arguments

Extract flags from command input:

Step 2: Validate Git State

Check that the repository is in a valid state for tagging:

Step 3: Compute New Version

Get current version and compute new version based on increment type:

Step 4: Display Summary

Show what will be deployed:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@benbrastmckie · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Parse Arguments

Extract flags from command input:

02
Step 2: Validate Git State

Check that the repository is in a valid state for tagging:

03
Step 3: Compute New Version

Get current version and compute new version based on increment type:

04
Step 4: Display Summary

Show what will be deployed:

05
Step 5: Execute Based on Mode

Dry-Run Mode If `--dry-run` is set: Force Mode If `--force` is set, skip confirmation and proceed to Step 6. Interactive Mode (Default)

06
Step 6: Create and Push Tag

Create the tag locally: Push the tag to remote:

07
Step 7: Update state.json

Update the deployment_versions section in state.json:

08
Step 8: Display Success

Show completion message with next steps:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.