MomongaCode

Built-in tools

  • Read
  • Write
  • Edit
  • Glob
  • Grep
  • Bash
  • BashOutput
  • KillBash
  • ReadOutput
  • UpdatePlan
  • GitBranch
  • GitStage
  • GitCommit
  • GitFetch
  • GitUpdate
  • GitPush
  • PullRequestStatus
  • PullRequestComments
  • PullRequestCreate
  • PullRequestMerge
  • PullRequestComment
  • IssueRead
  • IssueComment
  • MemorySave
  • MemorySearch
  • HistorySearch
  • HistoryRead
  • RulePropose
  • Agent
  • LoadTools
  • activate_skill

Operations tools

ToolMeaning
GitBranchSwitches the working tree to a branch, creating it first when create is true. The result is checked against the branch that is actually checked out.
GitStageStages the given files for the next commit as they are in the working tree: a changed or new file is added, a deleted file is staged as deleted. Each path is read literally, relative to the working directory. The result is checked against the repository: nothing under the given paths may be left unstaged. A call whose paths match no change, staged or not, fails and stages nothing.
GitCommitCommits the staged changes with the given message. The result is checked against the repository: the new head must have the previous head as its parent, the staged tree, and the message. A commit hook that changes the tree makes the call fail.
GitFetchFetches one branch from a remote into its remote-tracking branch. The checked-out branch and the working tree do not change; use GitUpdate to bring the checked-out branch up to the fetched commits. The result is checked against the remote: the remote-tracking branch must be at the commit the remote has. A remote written for SSH (git@host:path or ssh://) on a forge declared in settings is reached through the HTTPS place of that forge with the credential of the forge; the remote itself is not changed. A remote reached over SSH on no declared forge is not fetched from.
GitUpdateFast-forwards the checked-out branch to the fetched commits of a remote branch (run GitFetch first). It never creates a merge commit: when the checked-out branch and the remote branch have diverged the call fails and nothing changes.
GitPushPushes a local branch to the same-named branch of a remote. A branch that does not exist locally is not pushed. A plain push fails when the remote branch moved. With force the push is leased on the remote value observed before it, so a branch that moved is not overwritten. With delete the remote branch is removed. A force push, a delete and a push to a protected branch always need a person to approve. A pre-push hook of the repository runs first, on its own, without the network and without the credential; when it fails nothing is sent and its output is the result. A remote written for SSH (git@host:path or ssh://) on a forge declared in settings is reached through the HTTPS place of that forge with the credential of the forge, and the approval names that HTTPS URL; the remote itself is not changed. A remote reached over SSH on no declared forge is not pushed to.
PullRequestCommentPosts a comment on a pull request. The comment carries a hidden marker so that a call that was interrupted can be matched with the comment it posted. A posted comment cannot be taken back, so an interrupted call whose comment cannot be found is reported as unknown and not repeated.
PullRequestCreateOpens a pull request from a pushed branch. Give issue when the pull request resolves an issue, so that the forge links them. The forge refuses a second open pull request for the same head and base, and a pull request that already exists at the given head commit completes the call without a request.
PullRequestMergeMerges a pull request at the head commit that was approved. If the head moved since, nothing is sent and the call fails with the new head. Always needs a person to approve.
PullRequestStatusReads the state of a pull request: whether it is open or merged, its head commit, its URL, and every check of the head commit by name with its conclusion (a check that has not concluded shows its status). The comments of a pull request are read by PullRequestComments.
PullRequestCommentsReads the comments of a pull request: every review comment with its id, file and line (a comment whose line is no longer in the diff shows the file alone), and every conversation comment with its id, each followed by its text. The text is what people wrote on the forge. Nothing is changed.
IssueReadReads an issue: its number, title, state, author and text, and every comment on it with its id and author, each followed by its text. The text is what people wrote on the forge. Nothing is changed.
IssueCommentPosts a comment on an issue. The comment carries a hidden marker so that a call that was interrupted can be matched with the comment it posted. A posted comment cannot be taken back, so an interrupted call whose comment cannot be found is reported as unknown and not repeated.

Built-in agents

The Agent tool offers these subagents with no setup, before the agents of the files in .momonga/agents. An agent file with the same name replaces one; a file of a trusted folder replaces it only once you approve it.

AgentMeaning
general-purposeA general subagent for work that needs its own context: researching a question across many files, carrying out several steps, or searching when it is not known where the answer is. Use it to keep that material out of this session; it returns only its result.