Loading...
Loading...
Found 23 Skills
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.
[Hyper] Push unpushed commits to the remote. Discovers the current or descendant git repositories, checks for commits ahead of upstream, and pushes them. Use when the user wants to push, sync to remote, or send commits upstream.
Push projects to GitHub with three automatically determined modes: **First-time Push** (large file scanning → generate .gitignore → git init → create repo via gh → push), **Daily Update** (commit + push), **Version Release** (tag + create Release, optional attached download files). Core principle: Safety First: Must scan for large files and sensitive files before pushing, better to ask one more question than push something that shouldn't be pushed. Triggered when users say "push to GitHub", "git push", "upload to GitHub", "commit and push", "release version", "create release", "create tag", "/git-push". Not applicable for: Planning which features go into which version number (use issue-pool—this skill only handles tagging pre-determined version numbers), complex git operations like rebase/cherry-pick/resolving conflicts/modifying history/rolling back (use git commands directly, this skill does not cover these), self-testing and acceptance before code is completed.
Commit and push. Use when the user says "commit", "push", or "git push".
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
Stage all changes, generate a descriptive commit message from the diff, commit, and push to the current branch's upstream.
This skill should be used when the user asks to "commit changes", "craft a commit message", "stage and commit", "commit only session edits", or run a commit workflow with flags like --all, --deep, or --push. Creates atomic git commits with heuristic analysis, conventional-commit formatting, staging rules, optional deep analysis, and optional push.
Create atomic conventional git commit and push to remote repository. Use when committing staged changes with conventional commit format and immediately pushing to the remote branch.
Tidy workspace, create semantically meaningful commits, and push. Analyzes changes, categorizes files (commit/gitignore/delete/consolidate), groups into logical commits with conventional prefixes. Use when: ready to commit, cleaning workspace, pushing changes.
Create one or more Conventional Commits following the spec and push the current branch. Use when the user asks to create commits, write a conventional commit message, commit and push changes, or prepare commits before opening a pull request.
Git auto-commit tool. When users need to submit code changes, commit modifications, or submit after completing a task, this skill must be called to automatically generate a standardized commit message and execute the commit, with default push to the remote repository.
Commit changes and push to origin without creating a PR