agentleFS
Sign inStart free
TheEdoRanTheEdoRan/skills/skills/gcp/SKILL.md

gcp

Skill0 starsChanged 35 days agoMITView on GitHub

Stage changed files, create logical commits, split unrelated concerns into separate commits, push the current branch, and verify the result. Use only when the user explicitly invokes /gcp or $gcp or asks to run the GCP git workflow; accept any accompanying text as optional commit-message guidance.

  • Commits and pushes

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use firebase.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xfstudioSkill

    firebase

    Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. I

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 1

    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:

    Run the following workflow in the current repository.

    line 10
  2. Distinctive:

    Run git diff --stat and review the full relevant diffs.

    line 14
  3. Distinctive:

    Run git diff --cached --stat and review any already-staged changes.

    line 15
  4. Distinctive:

    Run git log --oneline -5 to learn the repository's commit-message style.

    line 16
  5. Distinctive:

    Run git branch --show-current and confirm it returns a branch name.

    line 17
  6. Distinctive:

    Treat any text supplied with the invocation as guidance for commit messages or grouping.

    line 18
  7. Distinctive:

    Create one commit when all changes form one cohesive feature or fix.

    line 20
  8. Distinctive:

    Create separate focused commits when changes span unrelated features, fixes, refactors, tests, or documentation.

    line 21
  9. Distinctive:

    Do not include unrelated untracked files or secrets.

    line 23
  10. Very specific:

    After all intended changes are committed, push with git push origin "$(git branch --show-current)".

    line 26
  11. Distinctive:

    Verify the push succeeded.

    line 27
  12. Distinctive:

    Never amend, force-push, reset, discard changes, bypass hooks, or change branches unless the user explicitly asks.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Git Workflow: Stage, Commit, and Push

Run the following workflow in the current repository.

  1. Inspect the repository before changing anything:
    • Run git status --short --branch.
    • Run git diff --stat and review the full relevant diffs.
    • Run git diff --cached --stat and review any already-staged changes.
    • Run git log --oneline -5 to learn the repository's commit-message style.
    • Run git branch --show-current and confirm it returns a branch name.
  2. Treat any text supplied with the invocation as guidance for commit messages or grouping. Do not let it override the requirement to inspect and logically separate changes.
  3. Group changes by concern:
    • Create one commit when all changes form one cohesive feature or fix.
    • Create separate focused commits when changes span unrelated features, fixes, refactors, tests, or documentation.
    • Preserve pre-existing staged changes. Do not unstage or rewrite them unless required to make the requested logical commits, and explain the reason if so.
    • Do not include unrelated untracked files or secrets.
  4. Stage each group explicitly with git add -- <paths>, inspect the staged diff with git diff --cached, then commit it.
  5. Match the recent commit-message style. If no clear style exists, use a concise imperative subject.
  6. After all intended changes are committed, push with git push origin "$(git branch --show-current)".
  7. Verify the push succeeded. Report the created commit or commits and show the final git status --short --branch and git log --oneline -5.

Never amend, force-push, reset, discard changes, bypass hooks, or change branches unless the user explicitly asks.

$ARGUMENTS

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.

Check your setup, free