agentleFS
Tony363Tony363/SuperClaude/.claude/skills/sc-push/SKILL.md

sc-push

Skill19 starsChanged 8 months agoMITView on GitHub

Multi-remote git push with selective content filtering. Push to multiple remotes with per-remote path exclusions, branch mapping, and force-push controls.

  • Deletes or force-pushes
  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Validate: - Check git state, uncommitted changes, remote existence

    line 32
  2. Distinctive:

    If uncommitted changes exist:

    line 67
  3. Distinctive:

    Ask if they want to commit first or push existing commits only

    line 69
  4. Distinctive:

    When paths must be excluded for a specific remote:

    line 88
  5. Distinctive:

    Stash uncommitted changes: if present

    line 90
  6. Distinctive:

    Restore stash: if applicable

    line 97
  7. Distinctive:

    Always confirm with user: before executing

    line 117
  8. Distinctive:

    Never force push to main/master without explicit user confirmation

    line 119
  9. Distinctive:

    Always show push plan: before executing

    line 159
  10. Distinctive:

    Bash: - All git operations

    line 167

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Multi-Remote Push Skill

Push changes to multiple git remotes with per-remote configuration. Supports selective content filtering (exclude paths per remote), branch mapping, and force-push controls.

Quick Start

# Push current branch to all remotes
/sc:push

# Push specific branch
/sc:push main

# Push with path exclusions for a remote
/sc:push --exclude efs:prompts/,secrets/

# Push to specific remotes only
/sc:push --remotes origin,staging

# Dry run to preview actions
/sc:push --dry-run

Behavioral Flow

  1. Parse - Extract branch, remote list, exclusions, flags
  2. Validate - Check git state, uncommitted changes, remote existence
  3. Plan - Build per-remote push plan with exclusions
  4. Confirm - Show plan and get user confirmation for force pushes
  5. Execute - Push to each remote sequentially
  6. Report - Summarize push results per remote

Flags

FlagTypeDefaultDescription
--remotesstringallComma-separated remotes to push to
--excludestring-Per-remote exclusions: remote:path1,path2
--dry-runboolfalsePreview push plan without executing
--forceboolfalseForce push to remotes with exclusions
--no-verifyboolfalseSkip pre-push hooks

Phase 1: Parse Arguments

  • Branch: First positional arg, or current branch via git rev-parse --abbrev-ref HEAD
  • Remotes: From --remotes flag, or all configured remotes via git remote
  • Exclusions: Parse --exclude remote:path1,path2;remote2:path3 format

Phase 2: Validate Git State

# Verify git repository
git rev-parse --is-inside-work-tree

# Get current branch
git branch --show-current

# Check for uncommitted changes
git status --porcelain

If uncommitted changes exist:

  • Warn the user
  • Ask if they want to commit first or push existing commits only

Validate each target remote exists:

git remote -v

Phase 3: Build Push Plan

For each remote, determine push strategy:

Simple Push (no exclusions)

git push <remote> <branch>

Filtered Push (with exclusions)

When paths must be excluded for a specific remote:

  1. Stash uncommitted changes if present
  2. Create temporary branch: git checkout -b tmp-push-<remote>-$$ <branch>
  3. Remove excluded paths from index: git rm -rf --cached <paths> (ignore errors if paths don't exist)
  4. Commit removal: git commit -m "tmp: remove excluded paths for <remote> push" --allow-empty
  5. Force push temp branch: git push <remote> tmp-push-<remote>-$$:<branch> --force
  6. Return to original branch: git checkout <branch>
  7. Delete temp branch: git branch -D tmp-push-<remote>-$$
  8. Restore stash if applicable

Present plan before executing:

Push Plan:
  Branch: <branch>

  Remote: origin
    Strategy: direct push
    Command: git push origin <branch>

  Remote: efs
    Strategy: filtered push (excluding: prompts/, secrets/)
    Steps: temp branch -> remove paths -> force push -> cleanup

Phase 4: Confirm

For any remote requiring force push:

  • Always confirm with user before executing
  • Show exactly what will be force-pushed and why
  • Never force push to main/master without explicit user confirmation

Phase 5: Execute Push

Execute push plan sequentially per remote:

  1. Push to each remote in order
  2. Report success/failure for each
  3. On failure: log error, continue with remaining remotes
  4. Clean up any temporary branches

Phase 6: Report Results

## Push Summary

| Remote | URL | Strategy | Status |
|--------|-----|----------|--------|
| origin | github.com/user/repo | direct | Success |
| efs | github.com/org/repo | filtered | Success |

**Branch**: <branch>
**Excluded paths**: efs: prompts/, secrets/

Error Handling

ScenarioAction
Not a git repoExit with error
Remote not foundError with available remotes
Uncommitted changesWarn, ask to commit or proceed
Push rejected (non-fast-forward)Suggest pull first, never auto-force
Force push to main/masterRequire explicit confirmation
Temp branch cleanup failsWarn user, provide cleanup command
Network failureReport which remotes succeeded/failed

Guardrails

  • Never force push to main/master without explicit user consent
  • Always show push plan before executing
  • Clean up temp branches even on failure
  • Restore stash even on failure
  • Dry run by default for filtered pushes on first use
  • Temporary commits never appear in the source branch history

Tool Coordination

  • Bash - All git operations
  • Read - Inspect .git/config for remote configuration

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.