Skip to content

lexwdex/specgit

v2.21.0MIT

SpecGit delivery workflow Skill for GitHub and GitLab: native Issue specifications, PR/MR delivery, checkpoints, and verified completion.

SpecGit plugin

SpecGit gives coding agents a shared delivery workflow for GitHub and GitLab. Issues hold the specification, a pull request or merge request gathers the selected Issues and the implementation, and the forge remains the source of truth for checks, review, merge, and closure.

This plugin is a thin distribution wrapper. It ships the specgit-native Skill and onboarding guidance only. It contains no native binary, installs no hooks, and writes no global state. The user-level specgit CLI remains a separate installation.

Requirements

The Skill drives the user-level specgit executable on your machine:

command -v specgit
specgit --version

You also need Git and an authenticated gh (GitHub) or glab (GitLab) session for forge operations.

If specgit --version fails, install the latest stable release from GitHub Releases:

# Download the ZIP for your system together with SHA256SUMS, then verify:
shasum -a 256 specgit-<version>-darwin-arm64.zip   # macOS
sha256sum specgit-<version>-linux-x64-gnu.zip      # Linux

The computed digest must match the corresponding row in SHA256SUMS. Stop and report the mismatch when the row is missing or does not match. Extract the archive, put the root-level specgit on a user-level directory in PATH, and confirm specgit --version. The specgit CLI binary is distributed only through GitHub Releases; the Skill/plugin is distributed through plugin marketplaces and .agents/skills. Do not use npm or unofficial mirrors.

No native Windows package is published. On Windows, install WSL (Windows Subsystem for Linux) yourself and use the Linux x64 package inside WSL.

The release asset verification reference records the Cosign signature command, the signed checksum manifest and the full verification contract. The agent installation guide covers installation through a coding agent, PATH setup and project initialization.

Install

The plugin bundles only a Skill and guidance, so every host still needs the user-level CLI from Requirements.

Claude Code

The repository hosts its own marketplace. Validate the plugin directory with claude plugin validate plugin --strict --profile directory, and the repository-root marketplace.json with claude plugin validate . --strict. Add the marketplace, then install the plugin:

claude plugin marketplace add LeXwDeX/SpecGit
claude plugin install specgit@specgit-marketplace

Inside a Claude Code session, the one-step form is:

/plugin install specgit --marketplace LeXwDeX/SpecGit

The one-step form requires Claude Code v2.1.275 or newer; on older versions use the two-step commands above.

Codex

The repository also hosts a marketplace entry in the documented Codex format:

codex plugin marketplace add LeXwDeX/SpecGit

Then use /plugins in Codex to browse and install specgit. This entry has not yet been exercised with a local Codex installation, so verify that the host loads the Skill before relying on it.

Pi, OpenCode and other hosts without SpecGit-installed hooks

These hosts may have their own plugin or extension mechanisms; SpecGit installs no host hook for them. The shared Skill under .agents/skills is how SpecGit integrates, and specgit init already installs it for the project; the default covers this, so no --agent flag is needed. To install one user-level copy instead:

specgit skill --user

That writes ~/.agents/skills/specgit-native/SKILL.md. You can also copy plugin/skills/specgit-native/ into a project's .agents/skills/ directory.

Use

Initialize the repository once with specgit init; existing projects use specgit setup and preserve recorded host choices. Then describe the work and the Skill loads automatically for Issues, pull/merge requests, branches, worktrees, checkpoints, CI or review follow-up, merge delivery, releases, and project status reviews. For example: "Implement issue 42, verify it, open a PR, and follow CI through merge."

Project hooks remain opt-in through specgit setup --hook-purpose guard or context; this plugin never installs hooks or global state.

Behavior and data disclosure

  • The plugin itself makes no network requests and stores no credentials.
  • The bundled Skill instructs the host agent to run the local specgit CLI.
  • That CLI reads and writes Issues, pull requests, and merge requests on GitHub or GitLab through your configured gh/glab credentials and the repository remote. It also reads CI status, reviews, branches, and checkpoints. Writes are limited to the task you authorize; previews such as --inspect, --dry-run, and --schema are available before changes.
  • No repository content is sent anywhere except the forge API selected by the repository remote.

License

MIT. See LICENSE.