git-push
Use when asked to push the current branch or its commits to the remote repository. Checks the worktree, upstream, outgoing commits, and existing authorisation before pushing.
- License 许可
- MPL-2.0
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- git-push
- description
- Use when asked to push the current branch or its commits to the remote repository. Checks the worktree, upstream, outgoing commits, and existing authorisation before pushing.
02 资源文件 1
- 参考文档agents/openai.yaml181 B
03 SKILL.md 正文
Pushing commits
Push commits to the remote repository.
Steps
- Run
git statusto check for uncommitted changes. Report them; a push sends commits only. Do not stage or commit those changes as part of a push request. - Determine the current branch and its upstream tracking branch. If no upstream is set, suggest setting one with
git push -u origin <branch>. - Run
git log @{u}..HEAD --onelineto show commits that will be pushed. If there are no new commits, inform the user and stop. - Show the commit list. Proceed if the user has already authorised pushing these commits to this destination. Otherwise ask for confirmation of that concrete push. Never proceed past an explicit instruction to hold off.
- Run
git pushto push the commits. - Report success or failure.
04 同仓库更多 Skills
writing-docs
Use when creating, rewriting, tightening, or reviewing any Modulus documentation — the documents under docs/ (introduction, architecture, core composition, data model, authn/authz, LTI, agent, deployment, security and privacy) and any per-package design notes. Trigger whenever the user asks to write, draft, improve, or review a doc; add a setup or getting-started section; document a subsystem, package, or API; or turn design notes into reference. Also use whenever a new subsystem ships and needs documenting, or a Planned document in 00-documentation-plan.md is being written. This skill encodes Modulus's documentation standard — doc-type selection, required structure, definition-before-use, runnable code examples, and house voice — so new and revised docs match the existing set rather than drifting from it.
github-pr
Open or update a GitHub pull request for the current branch — use when asked to create a PR, open a pull request, submit work for review, or push and PR. Handles branch naming, issue linking, and the PR description. Accepts an optional issue number or title hint as an argument.
git-commit
Create a git commit in this repository using the project's conventional commit format. Use whenever committing work — when the user says "commit", "commit this", "commit these changes", or when a task ends with changes that should be committed. Accepts an optional message hint as an argument.
writing-docs
Use when creating, rewriting, tightening, or reviewing any Modulus documentation — the documents under docs/ (introduction, architecture, core composition, data model, authn/authz, LTI, agent, deployment, security and privacy) and any per-package design notes. Trigger whenever the user asks to write, draft, improve, or review a doc; add a setup or getting-started section; document a subsystem, package, or API; or turn design notes into reference. Also use whenever a new subsystem ships and needs documenting, or a Planned document in 00-documentation-plan.md is being written. This skill encodes Modulus's documentation standard — doc-type selection, required structure, definition-before-use, runnable code examples, and house voice — so new and revised docs match the existing set rather than drifting from it.
typecheck
Use when asked to typecheck, check TypeScript, or verify type safety across the monorepo.
test
Use when asked to run or verify tests in this repository. Run one test when a file path is supplied, or the package test suites when no path is supplied.