Index of every page on this site: llms.txt
All skills
lassejlv avatar

/gitty

@72a388a
by Lasselassejlv/skills70 stars
2
Run it yourself

Use the gitty Rust CLI to inspect repository changes and generate repository-aware Git commit messages through Codex, Claude Code, or OpenCode. Use when an agent needs to preview staged or working-tree diffs, generate or refine Conventional Commit messages, select a provider or model, copy a message, configure gitty, create an authorized commit, or commit and push an authorized change.

Use this Skill: https://skilld.dev/gh/lassejlv/skills/gitty

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈99 tokens for metadata: the name and description. ≈797 when used: this file. ≈673 more on demand in 2 files.

Description uses 5.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈396 characters, or 5.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Gitty

Use gitty as the commit-message interface while keeping Git state changes within the user's authorization.

Run the workflow

  1. Confirm the working directory is the intended Git repository. Use gitty -C <path> ... when operating outside its root.
  2. Run gitty providers if provider availability is unknown. Auto mode falls through installed Codex, Claude Code, and OpenCode providers when one fails; an explicit --provider does not fall back. If gitty is missing, tell the user and offer the installation command from CLI reference; do not silently install software.
  3. Inspect the input with gitty diff before generation. Use gitty diff --stat for a compact view or gitty diff --all only when unstaged and untracked changes belong in scope.
  4. Generate with gitty gen. Add constraints such as --type, --scope, --hint, --style, or --provider only when they reflect the repository or user request.
  5. Return the generated message. Copy, commit, stage all changes, or push only when the user asked for that mutation.

Preserve repository safety

  • Treat plain gitty gen as read-only: it prints a message and does not modify the repository or remote.
  • Prefer staged changes for an authorized commit. Run gitty gen --commit only after confirming the intended changes are staged.
  • Use --all carefully because it includes and may stage staged, unstaged, and untracked changes. Inspect gitty diff --all first and exclude secrets, local configuration, generated artifacts, and unrelated user work.
  • Use --push only when the user explicitly asked to push. It implies a commit and pushes the current branch to its configured upstream.
  • Do not use --commit, --all, or --push merely because they are convenient. If authorization is ambiguous, generate the message and stop.
  • Rely on default credential redaction and inspect the exact redacted provider payload with gitty diff. Use --allow-secrets only when the user explicitly authorizes sending the raw diff and understands which provider will receive it.
  • Use --dry-run when the user wants to review the exact provider prompt. The prompt preserves the same default secret redaction.
  • Never invent success. Verify the resulting commit with git status --short and git log -1 --oneline; verify a requested push from command output or the remote state.

Choose inputs and output

  • Let the default auto selection use staged changes when present and otherwise visible working-tree changes.
  • Use --changes staged to force staged-only input.
  • Use --all or --changes all for every visible change only after checking scope.
  • Use -i for terminal-based selection, editing, regeneration, copy, commit, or push. Do not use interactive mode in a non-interactive shell.
  • Use --json when another program will consume candidate messages and -n 2 through -n 5 when alternatives help. A non-interactive commit requires exactly one candidate.
  • Use Conventional Commit --type and --scope only with --style conventional.

Read CLI reference for installation, configuration, providers, flags, and common command recipes.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    The skill facilitates the use of the `gitty` CLI tool to generate and manage Git commit messages. It involves installing a tool from the author's repository and processing local repository data with explicit user review and authorization steps.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: MEDIUM · 1 issue

Signed by skilld at 72a388a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 4 months ago

README badge

README badge for lassejlv/skills/gitty