repo-commit-and-push
Follows standard conventions for git commits and pushes, maintaining repository history cleanliness.
Install
mkdir -p .claude/skills/repo-commit-and-push && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16560" && unzip -o skill.zip -d .claude/skills/repo-commit-and-push && rm skill.zipInstalls to .claude/skills/repo-commit-and-push
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when committing or pushing changes in this repository. Create focused commits matching tpsp history, push only when requested, and push tags whenever pushing release work.Key capabilities
- →Push changes only when explicitly requested
- →Keep commits focused on one coherent purpose
- →Avoid staging unrelated user changes
- →Use conventional commit prefixes
- →Push tags when pushing release branches or tag-related work
How it works
This skill guides the user through inspecting `git status`, grouping files by purpose, staging them, running validation, committing with a focused subject, and pushing only when explicitly requested, adhering to conventional commit formats.
Inputs & outputs
When to use repo-commit-and-push
- →Committing focused fixes or features
- →Pushing release branches with tags
- →Standardizing commit history
About this skill
Repo Commit And Push
Use this skill when the task includes committing or pushing changes.
Policy
- Push only when the user explicitly asks.
- Keep commits focused on one coherent purpose.
- Do not stage unrelated user changes.
- Do not edit or commit generated output such as
bin/tpsp. - If pushing a release branch or tag-related work, push tags in the same work unit when appropriate.
Commit Format
Recent history mixes short imperative subjects with conventional prefixes such
as fix: and build:. Prefer conventional commits when the type is clear:
fix: handle API decode errors
build: update GoReleaser config
docs: document CLI examples
Use an imperative summary and add a short body when the change is not obvious.
Workflow
- Inspect
git status --shortand recent history. - Group files by purpose.
- Stage explicit paths for one group at a time.
- Run the validation relevant to that group before committing.
- Commit with a focused subject.
- Push only if requested by the user.
Never bypass hooks unless the user explicitly requests it.
When not to use it
- →When committing generated output like `bin/tpsp`
- →Bypassing hooks without explicit user request
- →Pushing without explicit user request
Limitations
- →Does not allow committing generated output
- →Does not bypass hooks without explicit user request
- →Does not push without explicit user request
How it compares
This skill enforces a structured commit and push policy, ensuring a clean, focused, and conventionally formatted commit history, unlike an unguided manual approach that might lead to inconsistent or unfocused commits.
Compared to similar skills
repo-commit-and-push side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| repo-commit-and-push (this skill) | 0 | 2mo | No flags | Beginner |
| github-manage | 6 | 9mo | Review | Beginner |
| tmux | 20 | 3mo | Review | Intermediate |
| jira | 11 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
github-manage
matteocervelli
Manage operations concerning GitHub on behalf of user
tmux
openclaw
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
jira
davila7
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
github-issues
github
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task.
triaging-issues
pytorch
Triages GitHub issues by routing to oncall teams, applying labels, and closing questions. Use when processing new PyTorch issues or when asked to triage an issue.
file-manager
Xxiii8322766509
文件管理技能。用于创建、移动、复制、删除文件和文件夹，整理目录结构。当用户需要管理文件、整理文件夹或批量处理文件时使用。