Use this skill only for AtomGit work. If the user only says "repo", "PR", "issue", "branch", or "tag" without saying AtomGit, do not assume this skill applies; confirm the platform first.
owner and reponumber for issues and pull requestsbranch, tag, path, or sha when the workflow needs themAtomGit MCP must be installed and configured outside this skill before the first AtomGit task. Do not wait until after a business request fails if the tool list already shows the server is missing, and do not ask users to paste tokens into chat.
This skill uses canonical AtomGit MCP method names such as atomgit_get_repository.
Some runtimes add extra namespace wrappers around MCP tools. Always use the exact tool name exposed by the current runtime instead of assuming a prefix format from an example.
| Identifier | Typical meaning | Notes |
|---|---|---|
| --- | --- | --- |
owner | Repository owner, username, or organization | Needed for most repository-scoped calls |
repo | Repository name | Needed with owner for most repository calls |
number | Issue or pull request number | Replaces older examples that used issue_number or pull_number |
path | Repository file path | Use with file-content and file-update calls |
sha | Commit or blob SHA | File updates usually need the current file SHA first |
page, perPage | Pagination controls | List endpoints often expose both |
references/setup-and-safety.md
共 1 个版本