メニュー
Present the status of the git repository to the user. Use to display the status of the repository after a successful git commit by the agent. The agent should not use this internally for its own needs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Fix lint, formatting, and prose issues in markdown files using Prettier and Vale. Use when the user or agent needs to fix lint, formatting, and prose issues in markdown files.
Autonomously select files to stage for an atomic Git commit. Use when the agent wants to stage selected files for a git commit. Only stages selected files, but does not commit them.
Iteratively, commit atomic changes to the respository. Use when the user or agent needs to autonomously commit atomic changes to the repository. Employs the "git-add", "git-message", and "git-status" in skills in sequence to perform the commit.
Generate a commit message for changes already in the Git staging area, and await approval from the user. Use when the agent needs to generate a commit message for staged changes. Only generates the commit message, but does not perform the commit.
Creates a new agent skill. Use when agent or user needs to create a new skill for the agent.
Format changelog and remove empty sections.
| name | git-status |
| description | Present the status of the git repository to the user. Use to display the status of the repository after a successful git commit by the agent. The agent should not use this internally for its own needs. |
GOAL: present the git status in a visually appealing and
consistent way.
WHEN: use after a successful git commit by the agent when it needs
to display the status of the repository to the user.
NOTE: The agent shouldn't use this internally for its own needs.
git status --porcelain=v2 --branch
The following reference file serves as a strict guideline:
references/git-status-unified.md: unified reference for parsing
git status output and presentation guidelinesIMPORTANT: To avoid a recursive loop, DON'T invoke the
git-status skill here.
git-status skill, get repository statusDONE