Gcp
My AI agent skills collection.
npx -y skills add TheEdoRan/skills --skill gcpAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.1 KB, as published. Nobody here has run it
Git Workflow: Stage, Commit, and Push
Run the following workflow in the current repository.
- Inspect the repository before changing anything:
- Run
git status --short --branch. - Run
git diff --statand review the full relevant diffs. - Run
git diff --cached --statand review any already-staged changes. - Run
git log --oneline -5to learn the repository's commit-message style. - Run
git branch --show-currentand confirm it returns a branch name.
- Run
- 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.
- 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.
- Stage each group explicitly with
git add -- <paths>, inspect the staged diff withgit diff --cached, then commit it. - Match the recent commit-message style. If no clear style exists, use a concise imperative subject.
- After all intended changes are committed, push with
git push origin "$(git branch --show-current)". - Verify the push succeeded. Report the created commit or commits and show the final
git status --short --branchandgit log --oneline -5.
Never amend, force-push, reset, discard changes, bypass hooks, or change branches unless the user explicitly asks.
$ARGUMENTS