About fstack-push
fstack-push is an agent skill for committing the current task’s changes and pushing the current branch. It limits staging to task-related files and reports the commit and push result.
Key features
- 01Stages only current-task changes
- 02Creates a concise commit message
- 03Pushes the current branch
- 04Reports commit and push status
- 05Avoids tests, deploys, and force-pushes
Use cases
- 01Commit and push completed task changes
- 02Push local commits when no changes remain
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/fstack-pushin Claude Code to confirm it loaded.
Details
From the project README/fstack-push
Commit the current task's changes, then push to the remote. That is the whole job.
When to use
- You want your current work committed and pushed, now.
- The user invokes
/fstack-push.
Steps
- Check the working tree. Separate the current task's changes from unrelated work. If the scope is unclear, stop and ask.
- Stage only the current task's changes and commit with a plain one-line message describing what changed. If the task is already committed, skip to the push.
- Push the current branch to its remote.
- Report what happened in one line: the commit (if any) and the push result.
Must NOT
- Run tests or deploy. This skill only commits and pushes.
- Commit unrelated changes.
- Force-push, or push to a different branch than the current one.
- Skip hooks.
- Amend commits that are already on the remote.
- Commit files that look like secrets —
.env, keys, credentials. Warn instead.
Example
User:
/fstack-pushAgent: "Committed 'Add export button to settings' and pushed to
main. Done."
User:
/fstack-push(nothing uncommitted)Agent: "Nothing to commit. Pushed the 2 local commits to
main."
Comments
Markdown supported