New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Commit

by LIDR-academy in LIDR-academy/AI4Devs-LTI-extended

Create focused commits and pull requests following repository standards.

MITAuto-check: notesDevelopment

Install Commit

skills CLI
$ npx skills add LIDR-academy/AI4Devs-LTI-extended --skill commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LIDR-academy/AI4Devs-LTI-extended commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LIDR-academy/AI4Devs-LTI-extended.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ai-specs/skills/commit .claude/skills/commit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
commit
GitHub stars
278
Token cost
~1.5k tokens
SKILL.md length
888 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Create focused commits and pull requests following repository standards.

  • Works in 7 steps: Description-only / no-git mode (check… → Inspect current state → Resolve scope: full commit vs… → …
  • Tasks that involve Pull requests
  • SKILL.md covers Instructions, 0. Description-only / no-git…, 1. Inspect current state and 2. Resolve scope: full commit…, plus 4 more sections
  • Calls git and gh

What it does

Commit is an agent skill from LIDR-academy/AI4Devs-LTI-extended. Create focused commits and pull requests following repository standards.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests and Commit messages. It works with Git. The repository describes itself as: Repository with several experiments from live sessions. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests
  • Tasks that involve Commit messages

Example prompts

  • “/commit”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Description-only / no-git mode (check first)
  2. Inspect current state
  3. Resolve scope: full commit vs feature-scoped commit
  4. Commit message
  5. Commit and push
  6. Pull Request
  7. Summary for the user

What it can do on your machine

Read from SKILL.md and the folder at commit 9ff9a80. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Commit loads about 1.5k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 888 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~20
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:52
    iles that should not be committed, e.g. `.env`, build artifacts, local config) as the scope for this commit.
  • NoteMentions a .env fileSKILL.md:69
    - Do not commit secrets, `.env`, or other sensitive or generated artifacts.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LIDR-academy/AI4Devs-LTI-extended at commit 9ff9a80, republished under its MIT licence (© LIDR-academy). 888 words, ~1,529 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
name
commit
description
Create focused commits and pull requests following repository standards.
author
LIDR.co
version
1.0.0

commit Skill

Use it when this workflow is required in the project.

Instructions

Role

You are an expert in version control and release workflows. You create clear, comprehensive commits and Pull Requests that align with project standards and make review and traceability straightforward.

Arguments

Optional. $ARGUMENTS may contain:

  • Nothing (empty): Stage and commit all relevant changes in the working tree, then open a single PR.
  • Feature/ticket identifiers: e.g. ticket IDs (e.g. SCRUM-123), branch names, or short feature labels. When provided, stage and PR only the changes that belong to those features; leave all other changes unstaged and uncommitted.
  • Description-only / no-git mode: If the user explicitly says something like "no PR", "only commit" (meaning only produce the commit text), "only description", "don't touch git", "just the message", or "dry run", then do not run any git commands or create a PR. Only determine scope, list what would be staged, and output the proposed commit message (subject + body). The user can copy and run git commands themselves.

Goal

  1. Produce a single, comprehensive commit that accurately describes the relevant changes.
  2. Push the branch and create (or update) a Pull Request for review.
  3. If arguments were given: stage and commit only the changes tied to those features; do not touch other modified files.

Process and rules

0. Description-only / no-git mode (check first)

If the user explicitly requested no git operations (e.g. "no PR", "only commit", "only description", "don't touch git", "just the message", "dry run"):

  • Perform only steps 1–3: inspect state, resolve scope (which files/hunks would be staged), and write the full commit message (subject + body).
  • Do not run git add, git commit, git push, or gh pr create. Do not modify the repository in any way.
  • Output for the user:
    1. List of files (and hunks, if partial) that would be staged.
    2. The proposed commit message in a copy-pasteable block.
  • Then stop; skip steps 4, 5, and 6.

1. Inspect current state

  • Run git status and git diff (and git diff --staged if needed) to list all modified, added, and deleted files.
  • Identify the current branch. If not on a feature branch, decide whether to create one from the base branch (e.g. main or develop) before committing.

2. Resolve scope: full commit vs feature-scoped commit

  • If $ARGUMENTS is empty or not provided

    • Treat all relevant changes (excluding files that should not be committed, e.g. .env, build artifacts, local config) as the scope for this commit.
    • Stage all of those and proceed to step 3.

  • If $ARGUMENTS is provided (e.g. ticket IDs or feature names)

    • Map each argument to the changes that clearly belong to it (by path, ticket id in branch name, or context in diffs).
    • Stage only the files/hunks that belong to those features.
    • Leave any other modified files unstaged and do not include them in the commit.
    • If a file contains both feature-related and unrelated changes, use git add -p (or equivalent) to stage only the hunks that belong to the requested features.
    • If no changes clearly match the given arguments, report this and do not commit.
Show full SKILL.md (378 more words)Show less

3. Commit message

  • Write the commit message in English (per docs/base-standards.md).
  • Make it descriptive (per Git Workflow in backend-standards.md and frontend-standards.md).
  • Structure it so that:
    • Subject line: Short, imperative summary (e.g. "Add candidate filters to position list", "Fix validation for application deadline"). Optionally prefix with a scope or ticket id (e.g. SCRUM-123: Add candidate filters).
    • Body (if needed): Bullet points or short paragraphs describing what changed and why (areas touched, new behavior, fixes). Reference ticket IDs here if they apply.
  • Do not commit secrets, .env, or other sensitive or generated artifacts.

4. Commit and push

  • Create the commit with the message from step 3.
  • Push the current branch to the remote (git push origin <branch>). If the branch does not exist on the remote, push with -u to set upstream.

5. Pull Request

  • Use the GitHub CLI (gh) for all GitHub operations (per develop-backend.md).
  • Create or update the PR for the current branch:
    • Title: Clear, aligned with the commit (e.g. include ticket ID if applicable: [SCRUM-123] Add candidate filters to position list).
    • Description: Summarize the change set, link to the ticket if relevant, and note any testing or follow-ups.
  • If the repo uses branch protection or required checks, mention that the PR is ready for review once checks pass.

6. Summary for the user

  • Report what was committed (files and scope).
  • If arguments were provided: confirm which features/tickets were included and that other changes were left unstaged.
  • Provide the PR URL (from gh output).

References

  • docs/base-standards.md: English-only for commit messages and technical artifacts.
  • docs/backend-standards.md and docs/frontend-standards.md: Git Workflow (feature branches, descriptive commits, small focused branches).
  • ai-specs/skills/develop-backend/SKILL.md: Use gh for GitHub and PR creation; optional ticket-based branch and PR linking.

Notes

  • Description-only: When the user asks for no PR or only the commit text, output the staging plan and message only; do not run any git or gh commands.
  • Do not run destructive git commands (e.g. git push --force without explicit user request).
  • If there are conflicts or the push is rejected, report the situation and suggest next steps (e.g. pull/rebase then push), but do not force-push unless the user asks.
  • When arguments are provided, only the changes tied to those features are staged and committed; everything else remains in the working tree for a separate commit or PR.

© LIDR-academy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in ai-specs/skills/commit of LIDR-academy/AI4Devs-LTI-extended.

Open the folder on GitHubat commit 9ff9a80

Compare with similar skills

Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit this skillLIDR-academy/AI4Devs-LTI-extended278—~1.5kAutomated safety check: NotesMIT
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Emoji Commit ConventionsbaptisteArno/typebot.io11k—~424Automated safety check: PassCustom licence
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0

Similar skills

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

  • Submit PR

    tisfeng/Easydict

    创建或复用当前 checkout 已提交变更的 GitHub PR，必要时推送任务分支。PR 审查使用 review-pr；仅本地提交使用 git-commit。

    15k GitHub stars~595 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from LIDR-academy/AI4Devs-LTI-extended

All 9 skills in this repo

  • Owasp Security Audit

    LIDR-academy/AI4Devs-LTI-extended

    A skill your agent uses when performing a cybersecurity audit, security review, OWASP Top 10 compliance check, vulnerability assessment, or preparing for a penetration test on a…

    278 GitHub stars~4.3k tokensUpdated 4 mo ago
    Auto-check: notes

  • Show Spec Working

    LIDR-academy/AI4Devs-LTI-extended

    A skill your agent uses when the user asks "show me X", "demo X", "walk me through X", "how X works" or requests a live feature demonstration from a spec, feature or ticket.

    278 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed

  • Sync Agent Symlinks

    LIDR-academy/AI4Devs-LTI-extended

    Analyze and synchronize agent skill exposure after ai-specs skill changes (additions, removals, renames).

    278 GitHub stars~1k tokensUpdated 4 mo ago
    Auto-check passed

  • Run Parallel Tasks

    LIDR-academy/AI4Devs-LTI-extended

    Run N feature tasks in parallel, each in its own worktree, following the full specboot pipeline (enrich → new → ff → apply → verify).

    278 GitHub stars~1.5k tokensUpdated 4 mo ago
    Auto-check passed

  • Explain

    LIDR-academy/AI4Devs-LTI-extended

    Teach underlying concepts with clear mental models to close skill gaps behind user questions.

    278 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed

  • Enrich Us

    LIDR-academy/AI4Devs-LTI-extended

    Analyze and enhance Jira user stories with complete, implementation-ready technical detail.

    278 GitHub stars~521 tokensUpdated 4 mo ago
    Auto-check passed

Works with

Categories

Questions about Commit

What does Commit do?

Create focused commits and pull requests following repository standards. Commit is an agent skill from LIDR-academy/AI4Devs-LTI-extended. Create focused commits and pull requests following repository standards.

When should I use Commit?

Commit fits situations like: tasks that involve Pull requests; tasks that involve Commit messages.

How do I install Commit in Claude Code?

Run `npx skills add LIDR-academy/AI4Devs-LTI-extended --skill commit -a claude-code`. Or copy the skill folder (ai-specs/skills/commit in LIDR-academy/AI4Devs-LTI-extended) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.

How do I install Commit in Codex?

Run `npx skills add LIDR-academy/AI4Devs-LTI-extended --skill commit -a codex`. Or copy the skill folder (ai-specs/skills/commit in LIDR-academy/AI4Devs-LTI-extended) into .agents/skills/commit in your project. Codex loads it when a task matches its description.

Can I use Commit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LIDR-academy/AI4Devs-LTI-extended --skill commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit, .gemini/skills/commit, .github/skills/commit and .opencode/skills/commit in your project.

What does Commit need to run?

Going by SKILL.md and its folder, Commit needs the command-line tools its instructions call (git and gh).

Does Commit access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Commit safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Commit use?

Commit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commit?

Skills that share tags, products or a category with Commit: Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit?

LIDR-academy (a GitHub organization) maintains it in LIDR-academy/AI4Devs-LTI-extended, which has 278 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on June 9, 2026.

Source: LIDR-academy/AI4Devs-LTI-extended on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.