Commit and push

Skill bakerstreetco/skills/commit-and-push

Reusable agent skills for real repository work: review, implementation, release, documentation, and project hygiene.

Install

npx -y skills add bakerstreetco/skills --skill commit-and-push

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

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

Commit and push only the changes made in the current work session while preserving unrelated worktree changes. Use when asked to commit, push, publish, save work in git, or prepare a clean commit without agent self-credit in the branch name, committer identity, or commit message.

SKILL.md

2.2 KB, as published. Nobody here has run it

Commit and Push

Use this skill to publish only the work from the current work session. Do not add agent branding, self-credit, or similar attribution to the commit message or committer identity.

Required Preflight

Before any command that changes history, reads/writes remotes, or depends on a hosting account:

Identify the active repository root with git rev-parse --show-toplevel.
Verify identity before acting:
- git config user.name
- git config user.email
- git remote -v
- gh auth status or the relevant hosting CLI account
Continue only when the active identity and remote match the intended repository account.

Never print secrets, tokens, private keys, or credential-helper output.

Commit Workflow

Inspect the worktree and recent style:

git status --short
git diff
git log -5 --oneline

Identify the exact files changed by the current work session. Exclude unrelated modified or untracked files from other sessions or user work.
Check whether repository conventions require official follow-up files in the same commit, such as changelogs, release notes, version fields, generated docs, lockfiles, or package metadata. Include them only when the repository clearly expects them for this change.
Stage explicitly:

git add -- path/to/file another/path

Do not use git add . or git commit -a.

Commit with a clean, descriptive message that reads naturally and contains no agent self-credit.
Run:

git pull --rebase --autostash
git push
git status --short --branch

Leave unrelated local changes untouched.

Reporting

In the final response, provide:

A simple title for the work.
One short sentence explaining what was done.
How the commit was isolated to the current work session's files.
Whether any official repo-wide follow-up files were included.
Any push or identity blocker, with the verification command that failed.