v0.1.4

Agents now pass on each repo's link with the report. The report always linked every repo, but agents that shortened it tended to drop the links; the verify step's instructions, its tool description and the skill now say to keep them.

claude mcp add --scope user git-for-me -- npx -y git-for-me

v0.1.3

A security release: zod 4.6.5 → 4.6.6, for GHSA-mrhx-c7xc-m3w5 (zod could exhaust memory validating oversized constrained collections). No change to what it does.

claude mcp add --scope user git-for-me -- npx -y git-for-me

v0.1.2

A release-process release: Git for Me! now publishes itself. No change to what it does.

claude mcp add --scope user git-for-me -- npx -y git-for-me

What changed

• Published from GitHub. Publishing a GitHub release now publishes the package to npm by Trusted Publishing (no token stored anywhere, with npm provenance), then server.json to the MCP Registry. It refuses a tag that doesn't match the version in every manifest, or a commit not on main.
• Antigravity: plugin/mcp_config.json for the Antigravity CLI, with an install section and a badge in the README.
• A privacy policy and terms of use (PRIVACY.md, TERMS.md).

v0.1.1

A branding release: the name is now Git for Me!, with the exclamation mark its hermit-crab mascot already had, in step with its companion Where My Hug At?. No change to what it does.

claude mcp add --scope user git-for-me -- npx -y git-for-me

What changed

• The name in the README, docs, plugin and extension manifests, and the social preview. The tool titles and the report heading read "Git for me!".
• The flow diagram's search step is now "Find git", matching Where My Hug At?'s "Find hug".
• Glama: a score badge in the README, and a glama.json naming the maintainer.

Package, command, repo and tool names (git-for-me, git_for_me) are unchanged.

v0.1.0

The first release. Odds are, most of what you want to build is already open
source. Tell your AI agent what you're making, and it finds it: which repos
to use as they are, which to adapt, and what's left for you to write, with
every repo it names checked live.

claude mcp add --scope user git-for-me -- npx -y git-for-me

Then ask: "Git for me: a CLI that pulls the tables out of PDF invoices into a spreadsheet."

What's in it

• Four questions first: stack, platform, license and upkeep, filled from
  the conversation or codebase where it can, asked where it can't.
• Searched, not remembered: each part of the job is searched on GitHub
  (most starred and rising in its topic, names and descriptions, README text),
  GitLab and Codeberg (topic and keyword). Anything the agent adds from
  memory ranks after the search's picks and is labeled.
• USE, ADAPT, BUILD, WRITE for each part, decided from what turned up.
• Checked live on each forge: repos that don't exist are dropped and the
  agent proposes others; the rest are flagged (archived, no license, own
  terms, copyleft, weak copyleft, stale, little used, fork, mirror).

Where it runs

• An MCP server for Claude Code, Codex, Copilot, Cursor, Gemini CLI, Cline,
  Devin and any MCP client (npx -y git-for-me).
• A plugin for Claude Code, Codex and Copilot CLI, and an extension for
  Gemini CLI.
• Over HTTP for Open WebUI (--http).
• An Agent Skill for anything that reads SKILL.md, with a shell fallback
  (rubric, search and verify).

Needs Node 22.18 or later. A GITHUB_TOKEN is optional and raises GitHub's
search limit from 10 a minute to 30. Full install options in the
README.