Name: git-commit
Author: isseis

Instruction file imported from isseis/tlsrpt-digest (.github/instructions/git-commit.instructions.md). Copyright stays with the author.

Get staged change git --no-pager diff --staged. If the output is empty, inform the user that there are no staged changes to commit and stop.
Propose commit message for it.

The commit message must be in English
The commit message must not contain backquote characters (`).
The commit message should be concise and descriptive.
One line summary + 3-5 bullets points would be expected. If the change is complex and large, longer and more detailed message is acceptable.
The commit message body should be broken down into lines every 80 characters (the summary line should remain a single line).

Ask confirmation for proceeding commit with y/n prompt
If a user lets move forward, commit the change git commit with the proposed commit message.

{ "ocm": "1", "id": "isseis-tlsrpt-digest-git-commit-instructions", "kind": "skill", "name": "git-commit", "description": "1. Get staged change `git --no-pager diff --staged`. If the output is empty, inform the user that there are no staged changes to commit and stop. 2. Propose commit message for it. - The commit message must be in English - The commit message must not contain backquote characters (`). - The commit message should be concise and descriptive. - One line summary + 3-5 bullets points would be expected. If the change is complex and large, longer and more detailed message is acceptable. - The commit message body should be broken down into lines every 80 characters (the summary line should remain a single line). 3. Ask confirmation for proceeding commit with y/n prompt 4. If a user lets move forward, commit the change `git commit` with the proposed commit message.", "publisher": "isseis", "version": "1.0.0", "capabilities": { "domains": [ "coding", "math" ], "tags": [ "skill-md", "github-instructions" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "1. Get staged change `git --no-pager diff --staged`. If the output is empty, inform the user that there are no staged changes to commit and stop. 2. Propose commit message for it. - The commit message must be in English - The commit message must not contain backquote characters (`). - The commit message should be concise and descriptive. - One line summary + 3-5 bullets points would be expected. If the change is complex and large, longer and more detailed message is acceptable. - The commit message body should be broken down into lines every 80 characters (the summary line should remain a single line). 3. Ask confirmation for proceeding commit with y/n prompt 4. If a user lets move forward, commit the change `git commit` with the proposed commit message." ], "primary": false, "metadata": { "source": { "provider": "github-instructions", "repository": "https://github.com/isseis/tlsrpt-digest", "path": ".github/instructions/git-commit.instructions.md", "ref": "e5f07eb6962271219d8d3d5fd0eb7c964bb06fe8", "url": "https://github.com/isseis/tlsrpt-digest/blob/e5f07eb6962271219d8d3d5fd0eb7c964bb06fe8/.github/instructions/git-commit.instructions.md", "key": "isseis/tlsrpt-digest/.github/instructions/git-commit.instructions.md" }, "applies_to": "**" }, "instructions": "1. Get staged change `git --no-pager diff --staged`. If the output is empty, inform the user that there are no staged changes to commit and stop.\n2. Propose commit message for it.\n - The commit message must be in English\n - The commit message must not contain backquote characters (`).\n - The commit message should be concise and descriptive.\n - One line summary + 3-5 bullets points would be expected. If the change is complex and large, longer and more detailed message is acceptable.\n - The commit message body should be broken down into lines every 80 characters (the summary line should rem", "cost": { "context_tokens": 193 } }

git-commit

About

Use it

Manifest

Reviews