mcp-server-ppt AGENTS.md

AGENTS.md

Guidance for AI coding agents working in this repository.

---

0. Repository identity — read this before anything else

This repository is trsdn/mcp-server-ppt. Every operation targets it and only it.

trsdn/mcp-server-ppt is registered on GitHub as a fork of sbroenne/mcp-server-excel, but that is metadata only. The two projects have completely diverged — they do not share a root commit, and upstream is unrelated spreadsheet automation code owned by someone else.

Never

• ❌ Open, close, comment on, or modify any issue or pull request in sbroenne/mcp-server-excel
• ❌ Add an upstream remote, or any remote pointing at a repository you do not own
• ❌ Merge, rebase, or cherry-pick from upstream
• ❌ Fetch upstream tags into this clone
• ❌ Report upstream issues or PRs as if they belonged to this project

Always

• ✅ Confirm the target repository before any gh command that reads or writes state
• ✅ Keep exactly one remote: origin → https://github.com/trsdn/mcp-server-ppt.git

Verify

git remote -v              # exactly one remote pair, both trsdn/mcp-server-ppt
gh repo set-default --view # trsdn/mcp-server-ppt
git tag                    # only this fork's tags (v1.0.0 - v1.0.3)

Repair if any check disagrees:

git remote remove upstream
gh repo set-default trsdn/mcp-server-ppt

Why this warning exists

gh derives its target from the git remotes. When an upstream remote is present it silently prefers the parent repository — so gh issue list and gh pr list return upstream's data with no indication that you are reading someone else's project.

This caused a real incident: an agent reported upstream issues #777 and #750 and PR #751 as belonging to this project, and was about to close issues in a repository it had no business touching. The correct answer was that this fork had zero open issues and zero open PRs.

The stale remote was also a live hazard — it carried a push URL, so a mistyped git push upstream would have written straight into another maintainer's repository.