# Reported issues for mcp-git-enhanced

Pod holds 6 of 6 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [mcp-git-enhanced](/mcp/mcp-git-enhanced).

## Most discussed

### Publish MCP registry entry

Prepare and publish the MCP registry entry after the npm package and GitHub release metadata remain stable.

Acceptance criteria:
- Validate server.json and mcp-registry.json against current registry expectations.
- Confirm npm package install command and package metadata.
- Document the registry publication process.
- Link the registry entry from the README after publication.

[Read the thread](https://github.com/davidweb3-ctrl/mcp-git-enhanced/issues/6) · 2026-06-02 · open · 1 comment

### Define review policy for future mutating Git tools

Define a maintainer review policy before adding any MCP tools that mutate repositories, branches, remotes, tags, releases, or working trees.

Acceptance criteria:
- Document which operations are intentionally read-only today.
- Define review requirements for future mutating tools.
- Require explicit user confirmation patterns for destructive or remote-affecting operations.
- Add tests or fixtures for confirmation and dry-run behavior once mutating tools exist.

[Read the thread](https://github.com/davidweb3-ctrl/mcp-git-enhanced/issues/7) · 2026-06-02 · open · 0 comments

### Add output size limits and sensitive-output warnings

Add guardrails for large command output and potentially sensitive Git output so maintainers can use the server more safely in AI-assisted workflows.

Acceptance criteria:
- Define output-size limits for tools that can return large diffs, logs, or file lists.
- Warn when output may contain secrets, tokens, private remotes, or local filesystem details.
- Prefer truncation with clear continuation guidance over unbounded output.
- Include tests for truncation and warning behavior.

[Read the thread](https://github.com/davidweb3-ctrl/mcp-git-enhanced/issues/5) · 2026-06-02 · open · 0 comments

### Add repository health report tool

Add a repository health report that helps maintainers inspect readiness signals before application, release, or contribution-review work.

Acceptance criteria:
- Report recent commits, open issues, open PRs, CI status, tags, releases, and package metadata when available.
- Surface missing OSS files such as SECURITY.md, CONTRIBUTING.md, ROADMAP.md, and issue templates.
- Keep all operations read-only.
- Include tests with mocked repository fixtures.

[Read the thread](https://github.com/davidweb3-ctrl/mcp-git-enhanced/issues/4) · 2026-06-02 · open · 0 comments

### Add release notes helper for commit ranges

Add a release helper that turns a Git commit range into grouped release-note draft content for OSS maintainers.

Acceptance criteria:
- Accept a base ref and head ref.
- Group changes by docs, fixes, features, tests, and maintenance when possible.
- Include warnings for untagged releases or dirty worktrees.
- Do not publish or tag automatically.

[Read the thread](https://github.com/davidweb3-ctrl/mcp-git-enhanced/issues/3) · 2026-06-02 · open · 0 comments

### Add PR review summary workflow

Add a maintainer-oriented workflow that summarizes a pull request's changed files, commit history, review status, and likely follow-up questions.

Acceptance criteria:
- Summarize PR metadata and changed files without mutating the repository.
- Highlight unresolved review comments when available.
- Keep output compact enough for Codex and ChatGPT review loops.
- Include tests for formatting and missing-field cases.

[Read the thread](https://github.com/davidweb3-ctrl/mcp-git-enhanced/issues/2) · 2026-06-02 · open · 0 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/davidweb3-ctrl/mcp-git-enhanced/issues).