Best use case
push is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Add all changes, commit, and push to GitHub
Teams using push should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/push/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How push Compares
| Feature / Agent | push | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Add all changes, commit, and push to GitHub
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Add, Commit, and Push Stage all changes, create a commit, and push to GitHub. ## Steps 1. Run `git status` to review what will be committed. Never use the `-uall` flag. 2. Run `git diff` to see staged and unstaged changes. 3. Run `git log --oneline -5` to see recent commit message style. 4. **Show the user the list of files that will be added/committed and ask for confirmation before proceeding.** If the user declines, stop. 5. If `$ARGUMENTS` is provided, use it as the commit message. Otherwise, analyze the changes and generate a concise commit message that describes **why** the changes were made. 6. Stage all changes: ```bash git add -A ``` 7. Create the commit. Always end the message with the co-author line: ``` Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> ``` 8. Push to the current branch: ```bash git push origin $(git rev-parse --abbrev-ref HEAD) ``` 9. If the push fails because the remote branch doesn't exist yet, push with `-u`: ```bash git push -u origin $(git rev-parse --abbrev-ref HEAD) ``` 10. Report the result — show the commit hash and confirm the push succeeded. ## Rules - Do NOT use `--force` or `--no-verify` flags. - Do NOT commit files that look like secrets (`.env`, credentials, tokens). Warn the user if any are staged. - If there are no changes to commit, tell the user and stop. - Always use a HEREDOC to pass the commit message to avoid quoting issues.
Related Skills
push-commit
Stage all changes, commit with a descriptive message, and push to the remote. Trigger with "push commit", "commit and push", "push changes", "/push-commit".
git-pushing
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
git-commit-push
This skill should be used when the user wants to commit their work to git and push to GitHub. It guides through reviewing changes, crafting meaningful commit messages following project conventions (including Conventional Commits when detected), creating commits with security checks, and pushing to remote repositories.
agentuity-cli-cloud-secret-push
Push secrets from local .env file to cloud. Requires authentication. Use for Agentuity cloud platform operations
agentuity-cli-cloud-env-push
Push environment variables from local .env file to cloud. Requires authentication. Use for Agentuity cloud platform operations
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
large-data-with-dask
Specific optimization strategies for Python scripts working with larger-than-memory datasets via Dask.
langsmith-fetch
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
langchain-tool-calling
How chat models call tools - includes bind_tools, tool choice strategies, parallel tool calling, and tool message handling
langchain-notes
LangChain 框架学习笔记 - 快速查找概念、代码示例和最佳实践。包含 Core components、Middleware、Advanced usage、Multi-agent patterns、RAG retrieval、Long-term memory 等主题。当用户询问 LangChain、Agent、RAG、向量存储、工具使用、记忆系统时使用此 Skill。
langchain-js
Builds LLM-powered applications with LangChain.js for chat, agents, and RAG. Use when creating AI applications with chains, memory, tools, and retrieval-augmented generation in JavaScript.
langchain-agents
Expert guidance for building LangChain agents with proper tool binding, memory, and configuration. Use when creating agents, configuring models, or setting up tool integrations in LangConfig.