Skip to content

sealad886/conventional-commit

v0.2.0MIT

Inspect dirty Git work, preserve excluded changes and staging, and create coherent verified Conventional Commits.

GitHubOpen Website

Conventional Commit

Version 0.2.0. One standalone skill for inspecting dirty Git work, selecting coherent changes, and creating verified local Conventional Commits while preserving excluded bytes and staging.

The skill accounts for staged, unstaged, untracked, binary, renamed, and generated content. It prevents unrelated pre-staged work from entering a plain commit, distinguishes path-only commits from mixed-hunk selection, respects hooks/signing, and reads back actual results. Advanced routes choose type/scope/breaking/revert semantics from actual behavior and configured automation, and commit an independent subset of already-staged text hunks through a verified alternate index while retaining original staging. No push, PR, merge, release, or worktree creation follows from a local commit request.

Install and use

In a Codex client supporting marketplace plugins:

codex plugin marketplace add sealad886/sealad886-codex-marketplace --ref main
codex plugin add conventional-commit@sealad886-codex-marketplace

Start a fresh task after installation. The root Agent Plugins 1.0 manifest also supports clients that discover portable skills from skills/.

This instruction-only plugin supports local and cloud tasks. It does not require a local executor or bundled server. The selected environment still needs access to the repository, Git, validation tools, and any required credentials. Account installation provides the cloud copy; the CLI command above installs locally.

Example requests:

  • "Use $conventional-commit:conventional-commit to commit my changes to this feature, preserving unrelated staged and unstaged work."
  • "Propose logical Conventional Commit groups without staging or committing."
  • "Choose a message for this configuration change, explain whether supported consumers must migrate, and check how our configured automation reads it. Do not commit or release."
  • "Commit only the first already-staged hunk in this file. Preserve the other staged hunk and unstaged edits; use the constrained subset procedure only if its independence and hook checks pass."
  • "Use $conventional-commit:conventional-commit --clean to commit the requested scope and discard only inspected unnecessary exclusions covered by that cleanup request."

Cleanup is off unless --clean is the first non-skill token immediately after the human's direct invocation. A later occurrence, quoted example, plugin description, or automatic loading does not enable it. Even valid cleanup preserves ambiguous ownership, valuable work, ignored data, and content outside the requested scope. A plan-only request remains read-only.

Requirements and included references

Needs a Git repository and the project's existing validation environment. No Python/runtime dependency, MCP server, external service, or companion plugin is required. Hooks and signing can require normal human credential interaction; the workflow does not disable them or alter global Git configuration.

The subset route is limited to independent staged text hunks at a captured HEAD, ordinary index layout, no concurrent writer, and audited hooks that do not change the candidate/index/working files. It leaves the real index untouched; selected unstaged edits and arbitrary reconciliation remain unsupported. Actual disposable Git fixtures covered preservation, empty/invalid selections, pre-commit/signing failures, concurrent changes, and unsafe hook detection. Git commands and suggestions are checked against installed capabilities and current Git documentation. Messages follow Conventional Commits.

Maintainer validation

From a checkout of the marketplace repository, use its source checker and distribution checker:

python3 scripts/check_plugin.py plugins/conventional-commit --layout source
python3 scripts/check_distribution_bundle.py plugins/conventional-commit

Check JSON/YAML, contained links/artwork, exactly one skill, manifest identity/ presentation parity, and fresh-client discovery. Static package validation does not prove agent execution, commit isolation, signing, or native visual rendering. See security boundaries and MIT license.