New: 98,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

Githits Release

by githits-com in githits-com/githits-cli

A skill your agent uses when maintaining the GitHits changelog or preparing, reviewing, or executing a GitHits release.

Apache-2.0Auto-check passedDevelopment

Install Githits Release

skills CLI
$ npx skills add githits-com/githits-cli --skill githits-release -a claude-code

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

GitHub CLI
$ gh skill install githits-com/githits-cli githits-release --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/githits-com/githits-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/githits-release .claude/skills/githits-release && 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
githits-release
GitHub stars
114
Token cost
~2.8k tokens
SKILL.md length
1,390 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when maintaining the GitHits changelog or preparing, reviewing, or executing a GitHits release.

  • Maintaining the GitHits changelog
  • SKILL.md covers Human Merge Gate, Release Checklist, MCP Registry and Agent Skills Lifecycle, plus 2 more sections
  • Calls bun, npx and git; reaches mcp.githits.com and githits.com
  • Executing a GitHits release

What it does

Githits Release is an agent skill from githits-com/githits-cli. Use when maintaining the GitHits changelog or preparing, reviewing, or executing a GitHits release. Covers continuous per-package release impact, version consistency, plugin manifests, MCP instruction quality, MCP registry publishing/versioning, and the special lifecycle for published Agent Skills.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Project-local skill for GitHits maintainers; not packaged for end users.

It sits in Development, covering MCP servers and Changelog and release notes. It works with Model Context Protocol. The repository describes itself as: CLI & MCP for GitHits - The Code Context Layer for AI Coding Agents. The licence is Apache-2.0.

When your agent uses it

  • Maintaining the GitHits changelog
  • Executing a GitHits release

Example prompts

  • “/githits-release”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Project-local skill for GitHits maintainers; not packaged for end users.

What it can do on your machine

Read from SKILL.md and the folder at commit 7449018. 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:

    • bun
    • npx
    • git

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • mcp.githits.com
    • githits.com

    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.

  • Compatibility

    Project-local skill for GitHits maintainers; not packaged for end users.

    From compatibility in the SKILL.md frontmatter.

Context cost

Githits Release loads about 2.8k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 1,390 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 githits-com/githits-cli at commit 7449018, republished under its Apache-2.0 licence (© githits-com). 1,390 words, ~2,783 tokens.

Download SKILL.mdSave it as .claude/skills/githits-release/SKILL.md (or your agent's skills folder).
name
githits-release
description
Use when maintaining the GitHits changelog or preparing, reviewing, or executing a GitHits release. Covers continuous per-package release impact, version consistency, plugin manifests, MCP instruction quality, MCP registry publishing/versioning, and the special lifecycle for published Agent Skills.
compatibility
Project-local skill for GitHits maintainers; not packaged for end users.
metadata.internal
true

Use this skill for GitHits changelog maintenance, release work, version-bump PRs, release-readiness reviews, and release notes.

Human Merge Gate

  • Release preparation ends with an open release PR. A request to audit, prepare, create, cut, or release a version does not authorize merging, enabling auto-merge, tagging, publishing, or waiting for publication.
  • Merge a release PR only after receiving separate, explicit human approval given after the release PR exists. The approval must explicitly authorize merging and identify that PR by number, URL, or an otherwise unambiguous reference to the already-open PR.
  • Earlier requests for an end-to-end release do not satisfy the merge gate. After opening the PR, report its URL and check status, then stop and ask for merge approval. Do not enable auto-merge as a substitute for approval.
  • After the separate approval, merge only the approved PR. The successful Main workflow will trigger publication, which may then be monitored to completion.

Release Checklist

  • Root githits and @githits/mcp have separate release flows. Bump both only when both surfaces changed.
  • For root githits releases, bump package.json and server.json, then run bun run plugins:generate to update .plugin/plugin.json, .claude-plugin/plugin.json, .claude-plugin/marketplace.json, .codex-plugin/plugin.json, .cursor-plugin/plugin.json, gemini-extension.json, the versioned portable/Antigravity plugin.json, and the versionless mcp_config.json adapter together.
  • For @githits/mcp releases, bump packages/mcp/package.json and its workspace version in bun.lock only when MCP package API, tool behavior, instructions, schemas, MCP auth/error behavior, or remote-server-facing public types changed.
  • For coordinated CLI and MCP releases, keep the MCP minor aligned with the CLI minor for discoverability. Start the first MCP release for a CLI minor at X.Y.0, then bump MCP patch for later MCP-package-visible changes in that CLI minor. Do not bump MCP for CLI-only changes.
  • After merge, the root release workflow and MCP release workflow both run from the successful Main workflow on main. The MCP workflow publishes only when @githits/mcp@<version> is not already on npm; use its manual workflow_dispatch path only for recovery or explicit dry runs.
  • The root release workflow also publishes server.json to the official MCP registry as com.githits/githits after npm publishes githits@<version>. Treat the MCP registry entry as part of the root githits release, not the @githits/mcp package release.
  • Keep server.json.version, the npm package entry version in server.json, and root package.json.version aligned. The release workflow rewrites a temporary registry manifest from package.json, but the committed server.json should still reflect the intended next root release for review and local validation.
  • Keep root package.json#mcpName equal to com.githits/githits; npm registry ownership validation depends on the published package manifest matching server.json.name.
  • Run or rely on package-scoped version checks to verify root plugin versions stay aligned and MCP versions are intentionally independent.
  • Reconcile the complete package-specific tag-to-HEAD delta with the files in changes/. Every fragment must name every public artifact and an explicit pending bump, including none for unaffected packages.
  • Run bun run plugins:generate, inspect the generated diff, and run bun run plugins:check before release-readiness signoff. Do not release with manually edited or stale generated assets.
  • Finalize the changelog before release. Group the fragments into a separate ## [<artifact> <version>] - YYYY-MM-DD section for each released artifact, then delete every consumed fragment.
  • Review public skills before signoff whenever user-facing CLI/MCP behavior changed. After the behavior is released or included in the same release branch, update skills/githits-code/SKILL.md, skills/githits-package/SKILL.md, and their references so skills.sh users get instructions that match the released surface.
  • Keep PR titles and labels release-note friendly; GitHub release notes are generated from merged PRs and .github/release.yml categories.
  • Run bun run build before release-readiness signoff. Run targeted smoke/eval commands when MCP tools, CLI commands, shared formatters, auth/error envelopes, Agent Skills, or agent-facing instructions changed.

MCP Registry

  • Registry name: com.githits/githits.
  • Registry server.json should list both supported transports when available: hosted remote MCP at https://mcp.githits.com and npm stdio via the root githits package with packageArguments equivalent to githits mcp start.
  • Do not encode npx githits@latest literally in server.json. The registry package entry uses runtimeHint: "npx", identifier: "githits", the exact release version, and package arguments. This represents the pinned release artifact, while docs can continue to show npx githits@latest mcp start for manual setup.
  • Publish to the MCP registry only after githits@<version> is published to npm, because registry validation checks the npm package metadata.
  • MCP registry publishing uses GitHub Actions OIDC, the production environment, and the Azure Key Vault-backed signer. Do not add an Azure client secret, Key Vault secret, exported signing key, npm token, or raw registry private key.
  • Required GitHub production environment secrets are identifiers used for masking and OIDC wiring: AZURE_TENANT_ID, AZURE_SUBSCRIPTION_ID, AZURE_CLIENT_ID, MCP_REGISTRY_KEY_VAULT_NAME, and MCP_REGISTRY_SIGNING_KEY_NAME. Do not print them, dump environment variables, or enable shell tracing.
  • Before releasing a registry update, verify mcp-publisher validate server.json locally with the pinned publisher version when practical.
  • Before the first registry publish, verify the domain proof is deployed at https://githits.com/.well-known/mcp-registry-auth.
  • For remote MCP auth, do not add static Authorization header metadata to server.json. The official registry remote transport schema supports URL, optional user-provided headers, and URL variables; OAuth is discovered from the remote MCP server through its WWW-Authenticate response and /.well-known/oauth-protected-resource metadata. Validate https://mcp.githits.com/.well-known/oauth-protected-resource returns 200 and unauthenticated remote MCP requests return the expected 401 with resource_metadata.
Show full SKILL.md (551 more words)Show less

Agent Skills Lifecycle

  • User-facing skills under skills/ are picked up by skills.sh from main, not from npm release artifacts.
  • Do not update skills/ to describe unreleased CLI/MCP behavior, except for the bounded githits-mcp stable-guide rule below. A merge to main can expose those skill instructions immediately.
  • For the githits-mcp stable guide, exact parity is a bounded exception: when backing stable behavior or buildMcpQuickStart() changes, update the backing behavior, builder, and embedded terminal guide copy in the same PR, merge that PR to main, and ship it in the next applicable release cycle. This accepts the bounded main-to-release window for skills.sh; it does not create a deploy-first or two-PR flow. buildLocalMcpQuickStart() runtime appendices remain excluded from the public copy.
  • githits-onboarding keeps its separate release-branch rule: update the public skill only on the release branch after the corresponding CLI behavior is included, so skills.sh does not advertise unreleased onboarding behavior.
  • After the backing CLI/MCP behavior is released or part of the release being prepared, update skills/ so skill descriptions, decision flows, examples, detailed references, and command-to-MCP mappings match the released surface.
  • When MCP instructions, tool descriptions, or guardrails change, review skills/githits-code/SKILL.md, skills/githits-package/SKILL.md, and their references for parity. Keep MCP instructions as the quality baseline; they are currently strong and should not be weakened casually.
  • After changing public skills or plugin-facing guidance, run bun run plugins:generate and bun run plugins:check so every host manifest remains aligned with the canonical root surface.
  • If a skill update is intentionally delayed until after release, note that in the release/change plan so it is not forgotten.

Changelog Fragments

  • Follow docs/implementation/release-process.md and changes/README.md; every notable change owns a new independent fragment under changes/ rather than editing CHANGELOG.md.
  • Use git log and merged PRs since each package's previous tag to audit the fragments and find omissions before release; fragments do not replace range review.
  • Record the pending SemVer impact for githits, @githits/mcp, and every future independently versioned public artifact in each fragment. Keep unaffected packages explicit as none.
  • During release preparation, compute each artifact's aggregate bump from the highest impact in its fragments, group affected entries by category into that artifact's versioned section, and delete all consumed fragments. Never partially consume a cross-artifact fragment; leave unrelated fragments untouched. Consume all-none repository entries with the next root githits release.
  • Treat dated, versioned sections as immutable historical records. Change one only for a blatant, demonstrable factual error and make the smallest correction that restores accuracy; wording improvements and omitted minor details do not qualify.
  • Exclude purely internal refactors unless they affect users, agent behavior, performance, or reliability.
  • Call out changes that require users or agents to adjust commands, flags, config, auth setup, environment variables, MCP setup, or skill usage.
  • Mention known limitations or intentionally deferred skill updates when they affect current users.

Guardrails

  • Do not expose credentials while verifying release/auth flows.
  • Do not force-push, amend, or rewrite release history unless explicitly requested.
  • Refuse historical changelog cleanup or expansion unless the existing text is blatantly factually wrong.
  • If fragment impacts, package manifests, or the verified package-visible delta disagree, stop and reconcile them before release signoff.
  • If root package and plugin manifests disagree, stop and fix them before a root githits release.
  • If @githits/mcp changed but its package version did not, stop and either bump it or document why the change is not MCP-package-visible.

© githits-com, Apache-2.0. 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 .agents/skills/githits-release of githits-com/githits-cli.

Open the folder on GitHubat commit 7449018

Compare with similar skills

Githits Release 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.

Githits Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Githits Release this skillgithits-com/githits-cli114—~2.8kAutomated safety check: PassApache-2.0
ReleasePrefectHQ/fastmcp28k—~2.9kAutomated safety check: PassApache-2.0
Reading Livekit Docslivekit-examples/agent-starter-python2641 repos~1.1kAutomated safety check: PassMIT
MCP Server Trello Releasedelorenj/mcp-server-trello445—~3.5kAutomated safety check: PassMIT
Suede Launch PackagingJasonColapietro/suede-creator-skills127—~2.4kAutomated safety check: PassMIT
Release Prepjohnhuang316/code-index-mcp1k—~680Automated safety check: PassMIT

Similar skills

  • Release

    PrefectHQ/fastmcp

    Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Reading Livekit Docs

    livekit-examples/agent-starter-python

    Looks up current LiveKit facts (API signatures, CLI flags, config options, model and provider support, SDK changelogs, pricing) from the docs instead of answering from memory.

    264 GitHub starsUsed in 1 repo~1.1k tokens
    DevelopmentAuto-check passed

  • MCP Server Trello Release

    delorenj/mcp-server-trello

    Canonical build → release → tag → publish procedure for the @delorenj/mcp-server-trello repo.

    445 GitHub stars~3.5k tokensUpdated 14 days ago
    DevelopmentAuto-check passed

  • Suede Launch Packaging

    JasonColapietro/suede-creator-skills

    Suede-owned launch packaging and install verification. An agent skill from JasonColapietro/suede-creator-skills.

    127 GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Release Prep

    johnhuang316/code-index-mcp

    A skill your agent uses when code-index-mcp implementation is complete and a version bump, release notes, tag, package publication, or GitHub release is being prepared.

    1k GitHub stars~680 tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • MCP Apps Sync Docs

    apollographql/apollo-mcp-server

    Syncs MCP Apps documentation with the @apollo/client-ai-apps changelog.

    311 GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from githits-com/githits-cli

  • Githits Code

    githits-com/githits-cli

    A skill your agent uses whenever invoking the GitHits CLI for public OSS source, documentation, or example evidence, including code search/grep, file navigation, source verification, docs lookup, or…

    114 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Githits Onboarding

    githits-com/githits-cli

    A skill your agent uses when the user asks to install, connect, configure, sign in to, sign up for, or start using GitHits.

    114 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Githits Package

    githits-com/githits-cli

    A skill your agent uses whenever invoking the GitHits CLI for public package or dependency evidence, including metadata, versions, licenses, vulnerabilities, dependency graphs, changelogs, release…

    114 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Braintrust Agent Evals

    githits-com/githits-cli

    Inspect, query, compare, or explicitly export GitHits agent-eval history in Braintrust using the repository's verified workflow.

    114 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Githits Plugin Maintenance

    githits-com/githits-cli

    Internal repository-maintenance skill for GitHits cross-host plugin and Agent Skill surfaces.

    114 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Githits MCP

    githits-com/githits-cli

    Route public OSS code, documentation, examples, and package questions to GitHits tools.

    114 GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Githits Release

What does Githits Release do?

A skill your agent uses when maintaining the GitHits changelog or preparing, reviewing, or executing a GitHits release. Githits Release is an agent skill from githits-com/githits-cli. Use when maintaining the GitHits changelog or preparing, reviewing, or executing a GitHits release.

When should I use Githits Release?

Githits Release fits situations like: maintaining the GitHits changelog; executing a GitHits release.

How do I install Githits Release in Claude Code?

Run `npx skills add githits-com/githits-cli --skill githits-release -a claude-code`. Or copy the skill folder (.agents/skills/githits-release in githits-com/githits-cli) into .claude/skills/githits-release in your project. Claude Code loads it when a task matches its description.

How do I install Githits Release in Codex?

Run `npx skills add githits-com/githits-cli --skill githits-release -a codex`. Or copy the skill folder (.agents/skills/githits-release in githits-com/githits-cli) into .agents/skills/githits-release in your project. Codex loads it when a task matches its description.

Can I use Githits Release 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 githits-com/githits-cli --skill githits-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/githits-release, .gemini/skills/githits-release, .github/skills/githits-release and .opencode/skills/githits-release in your project.

What does Githits Release need to run?

Going by SKILL.md and its folder, Githits Release needs the command-line tools its instructions call (bun, npx and git). Our summary lists: Node.js. Compatibility (from SKILL.md): Project-local skill for GitHits maintainers; not packaged for end users..

Does Githits Release access the network?

SKILL.md names 2 domains. In commands or code: mcp.githits.com and githits.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Githits Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Githits Release use?

Githits Release is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Githits Release use?

About 2.8k tokens (SKILL.md is roughly 11k 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 Githits Release?

Skills that share tags, products or a category with Githits Release: Release (PrefectHQ/fastmcp, 28k stars), Reading Livekit Docs (livekit-examples/agent-starter-python, 264 stars), MCP Server Trello Release (delorenj/mcp-server-trello, 445 stars) and Suede Launch Packaging (JasonColapietro/suede-creator-skills, 127 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Githits Release?

githits-com (a GitHub organization) maintains it in githits-com/githits-cli, which has 114 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

Source: githits-com/githits-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.