send

Other Community

Skill notes

Argument Handling

Parse $ARGUMENTS (appended at the bottom of this skill) to extract the user's intent. No arguments: Proceed normally -- auto-generate everything. Arguments provided (e.g., feat: add repo argument support to prime command): Store as INTENT and use it throughout: Branch name (Phase 0d): derive a slug from the intent

Prerequisites

git -- version control Remote CLI (auto-detected from remote URL): GitLab remotes (opengroup.org, gitlab): requires glab GitHub remotes (github.com): requires gh Optional (graceful degradation if absent):

0a. Check for changes (bail early if nothing to send)

If clean, also check for unpushed commits: If both are clean, STOP -- nothing to send. If there are unpushed commits but no local changes, skip to Phase 4 (Push).

0b. Detect environment

Run these checks. The results gate all later phases. Remote platform: Bare repo / worktree layout: This matters for branch naming -- bare repos cannot use slashes in branch names because they create subdirectories under .bare/refs/heads/ which may conflict or fail.

0d. Branch safety

Branch naming rules (gated by IS_BARE_WORKTREE): IS_BARE_WORKTREE=true: use flat names with hyphens (e.g., add-repo-argument-support) IS_BARE_WORKTREE=false: use slashed names (e.g., feature/add-repo-argument-support) On main or master: These are release branches -- changes must go on a feature branch.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
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
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

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

01
Phase 0: Preflight

Phase 0: Preflight

02
Phase 1: Lite Code Review

A quick sanity check -- catch obvious problems before they become review comments. View the full diff: Scan the changes for: Hardcoded secrets, credentials, API keys, `.env` files Files that should not be committed: binaries, `.tfstate`, `.env`, credential files

03
Phase 2: Quality Checks

Run checks based on which file types changed -- skip checks that don't apply. Only run a check if the relevant tool is available. Terraform (`.tf` files changed): YAML (`.yaml` or `.yml` files changed): JSON (`.json` files changed):

04
Phase 3: Commit

Stage changes and create a conventional commit. The method depends on which tools are available (detected in Phase 0b). If INTENT is available and already follows conventional commit format, prefer using it as the commit message rather than auto-generating -- the user told you what this change is.

05
Phase 4: Push

Push the branch to the remote:

06
Phase 5: Merge / Pull Request

Phase 5: Merge / Pull Request

Discussion

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