SkillFoxx

GitX skill

A skill that splits changes into logical Conventional Commits and safely handles branches, pushes and pull requests.

  • 105 ★ on the repository
  • Last commit
  • MIT
Skill

Extended access

Why this level

  • The skill creates commits, branches, pull requests and issues and pushes to origin, so each such action should be reviewed before confirmation.
All reasons and checks

musoyangrigor/gitx-skillAuthor:musoyangrigor

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/gitx

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The skill creates commits, branches, pull requests and issues and pushes to origin, so each such action should be reviewed before confirmation.

This is third-party code. Review the repository files before installing.

What it does

GitX is a portable Git workflow skill for AI agents. The `$gitx` command inspects the working tree, splits changes into logical groups and creates commits in Conventional Commits format. If several groups appear, the agent asks whether to make separate commits or one. Around commits the skill has commands for branches with `feat/` and `fix/` prefixes, safe `pull` and `push`, GitHub pull requests and issues, and merge or rebase conflict resolution. `scan` looks for secrets in changes and history, `doctor` diagnoses common Git problems and `plan` previews commit groups without changing anything. Project preferences live in `.gitx.json`.

Who it is for. Developers who edit code with Codex, Claude Code or Cursor and end up with a pile of unrelated changes in the working tree.

Good fit when

  • After a long agent session the tree holds edits for different tasks that must be split into commits.
  • Before a push, changes and history must be checked for secrets that slipped in.
  • Branch, checks, commit, push and pull request should go through one `$gitx ship` command.
  • A rebase stopped on a conflict and the agent needs a resolution routine.

Not a fit when

  • You need one commit from one edit: plain `git commit` is enough.
  • The team uses its own message format instead of Conventional Commits.
  • Work happens without GitHub: pull requests and issues are created only there.

Example request

$gitx plan — show how you would split my changes into commits without changing anything.

Limitations

Pull requests and issues need GitHub and access to it on the machine. The commit message format is fixed to Conventional Commits. Before `amend` the skill asks for confirmation, and `$gitx scan` only reports findings and changes nothing. Repository tests run through `python3 -m unittest discover -s tests -v` and need Python 3 and Git. The skill is invoked through the agent skills interface, and a new session starts after installation. The last commit in the repository was made in October 2026.

How to disable. Delete the gitx skill folder from your agent's skills directory. The `.gitx.json` file in project repositories stays and is removed by hand.

FAQ

How do I install GitX?

Run `npx skills add musoyangrigor/gitx-skill --skill gitx`. The Skills CLI configures the skill for the selected agent; start a new session afterwards.

What does a bare `$gitx` call do?

It immediately inspects the repository and creates a smart commit. The command list shows only when you ask for help.

How do I implement an existing issue?

Pass the number: `$gitx issue 123`. Any other text after `issue` creates a new GitHub issue.

How do I set the base branch for pull requests?

Run `$gitx setup` and save `prBase` in `.gitx.json`. An explicit command such as `$gitx ship main` overrides the saved value.

How do I check a repository for secrets?

Run `$gitx scan`. The skill looks for secrets and sensitive files in changes and history, reports findings and a secret-exposure rating and changes nothing.

Discussion

No questions or reviews yet.

Skills

A skill and plugin for Git and GitHub: branches, Conventional Commits and a pull request path to a green merge.

SkillExtended access59

A CLI and skill for precise non-interactive git: commit single hunks, split commits and fold fixes into earlier ones.

CLIBroad access192

gitai is an open source-control server for hundreds of agents: landing by compare-and-swap, server-side history and the graft CLI.

CLIExtended access1K
Official

The prek skill teaches an agent to set up Git hooks with prek, a Rust replacement for pre-commit: config, shims, priorities, built-in hooks and monorepos

SkillBroad access8.8K

A GitHub CLI wrapper for agents: compact TOON output, next-step hints and structured errors for issues, PRs, CI and releases

CLIBroad access364

A Git client with a built-in MCP server for Windows, macOS and Linux: an agent reads repos, PRs, issues and CI logs, read-only

MCP serverBroad access248

README in short

The skill lives in the `gitx/` folder and follows the Agent Skills format: `SKILL.md`, references for pull requests, issues, secret scanning, ship and diagnosis, and a `gitx.schema.json` schema. Tests use disposable Git repositories.

README badge

Original SKILL.md

---
name: gitx
description: "Portable Git workflow skill for AI coding agents that turns messy AI-generated changes into clean Git history. Use for smart Conventional Commits, logical commit splitting, branches, checks, pull and push, GitHub PRs and issues, secret scanning, commit planning, Git status and history, repository diagnosis, and merge or rebase conflict resolution with Claude Code, OpenAI Codex, Cursor, and other Agent Skills-compatible tools."
---

# GitX

## Default action

On a bare invocation—`$gitx`, `gitx`, or a skill-UI invocation with no extra command—immediately execute the Smart commit workflow. Make the first action a repository inspection with Git status and the relevant diff. After inspecting, create the appropriate commit or report that there is nothing to commit.

Treat a bare invocation as an action, never as a help request. Do not announce that GitX was loaded, list commands or examples, ask which command to run, or wait for more instructions. Show the command list only when the user explicitly asks for help or available commands.

## Commands and dispatch

Match natural-language requests to the commands below. Route “check my changes” or “show git status” to Status when the user wants a read-only summary; route “run tests before committing” to Checks. Use Doctor for Git workflow diagnosis and Plan for a commit preview. Read supporting references only when their workflow or loading condition applies.

Route `gitx issue` by argument shape, not by the intent implied by its wording. An argument containing only an issue number, such as `123` or `#123`, selects the existing-issue implementation workflow. Treat every other non-empty argument as a description for a new GitHub issue, even when it contains words such as “fix,” “update,” or “resolve.” With no argument, ask for the issue description. Never implement a problem supplied as a non-numeric `gitx issue` description.

`gitx issue <description>` explicitly requests publication to GitHub. Repository-local tracker conventions do not redirect this command to local files; follow the [GitHub issue creation workflow](references/github-issues.md#create-a-new-issue), including its failure handling.

For `gitx ship [base]`, the optional argument is the PR's destination branch, never the name of a new feature branch. For example, `gitx ship dev` targets `dev`. Dispatch to Ship, not directly to Branch or Pull requests.

| Command | Action |
| --- | --- |
| `gitx` | Create a smart commit. |
| `gitx setup` | Preview and save project preferences in the repository's `.gitx.json`. |
| `gitx body` | Create a smart commit with a useful commit body. |
| `gitx branch [name]` | Create and switch to a branch. |
| `gitx branch check` | Create a default branch, run checks, then create a smart commit. |
| `gitx pull` | Safely pull updates for the current branch. |
| `gitx push` | Push the current branch to `origin`. |
| `gitx pr [base]` | Create a GitHub pull request into the supplied, configured, or default base branch. |
| `gitx ship [base]` | Create a feature branch when needed, run checks, commit, push, and open a PR into the supplied, configured, or default base branch. |
| `gitx issue <description>` | Create a GitHub issue with a generated title and body. |
| `gitx issue <number>` | Fix the GitHub issue with that number. |
| `gitx resolve` | Resolve an in-progress merge or rebase conflict. |
| `gitx check` | Run relevant checks, then create a smart commit. |
| `gitx status` | Show Git status and changed-file summary; make no changes. |
| `gitx doctor [problem]` | Diagnose repository problems and suggest next steps; make no changes. |
| `gitx tree` | Show a compact Git history tree and repository context; make no changes. |
| `gitx scan` | Scan changes and history for exposed secrets and sensitive files; make no changes. |
| `gitx plan` | Preview the proposed commit groups and messages; make no changes. |
| `gitx type <type>` | Create a smart commit using the given Conventional Commit type. |
| `gitx scope <scope>` | Create a smart commit using the given scope. |

Report a problem