Commit local changes to the current Git branch with a message based on the project's conventions. When staged and unstaged changes coexist, choose which to include. The skill does not push changes or create pull requests.
Commit local changes without pushing.
Review the instructions the agent will receive before you install.
Commits local changes to the current branch. Does not push or create a PR.
Run git status --porcelain and inspect the output:
git add -A first.git add -A to stage
everything, then commit.Read the staged diff (git diff --cached) and generate a commit message
following the project's commit conventions. If no convention is found, default
to a concise English message under 120 characters ending with a period, with no other punctuation, focusing on user-perceivable changes.
Commit, then output a single line in the format:
已提交 {short_hash}：{commit message}
If the user chose partial, also inform them that unstaged changes remain and were not included in this commit.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Accept screenshot baseline changes by running the project's dedicated script, then commit the updated version.json using the project's commit conventions. This provides an explicit command for recording changes to the screenshot comparison baseline.
Review local branches, pull requests, commits, or files and address issues. The skill selects a single-agent or multi-agent workflow based on the environment, with automatic fixes for lower-risk issues and confirmation for high-risk changes.
Create PAGX vector graphics files from a visual description, HTML file, or public URL, including supported animations. Edit existing designs, check their appearance, and export them to SVG, HTML, or PPTX.
Commit and push local changes, then create a pull request or update an existing one based on the branch state. The skill prepares commit messages and new pull request details from the changes being submitted.
Review a branch's commits, combine adjacent changes that belong together, and improve commit messages. A rebuilt history is prepared separately and replaces the original branch only after the user reviews and confirms the proposed changes.