Agent Skills
› anyproto/anytype-ts
› commit-push
commit-push
GitHub自动化完成Git代码提交与推送流程。检查状态、安全暂存文件、生成符合规范的提交信息(含Co-Authored-By)、执行提交并推送到上游分支,全程禁止强制推送或跳过钩子,确保操作安全合规。
Trigger Scenarios
用户要求一次性提交并推送代码变更
需要遵循特定命名规范和安全规则进行Git操作
Install
npx skills add anyproto/anytype-ts --skill commit-push -g -y
SKILL.md
Frontmatter
{
"name": "commit-push",
"description": "Commit staged\/unstaged changes and push to the remote branch in one step"
}
Commit & Push Skill
Commit all current changes and push to the remote in a single workflow.
Process
- Check state — Run
git status(no-uall),git diff(staged + unstaged), andgit log --oneline -5in parallel - Abort if clean — If there are no changes, inform the user and stop
- Stage files — Add changed files by name (never use
git add -Aorgit add .). Skip files that look like secrets (.env, credentials, tokens) - Draft commit message — Follow the repo's
JS-XXXX: short descriptionconvention. Summarize the "why", not the "what" - Commit — Use a HEREDOC for the message. Always append the co-author trailer:
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> - Push — Push to the current remote-tracking branch (typically
origin/develop). Usegit push(never force-push) - Confirm — Show the resulting commit hash and remote status
Rules
- Never amend existing commits
- Never force-push
- Never skip hooks (
--no-verify) - Never commit files that contain secrets
- Always create a NEW commit, even after a hook failure
- Push target is always the current branch's upstream (usually
develop)
Version History
- 10f2692 Current 2026-07-25 08:56


