메뉴
Use when creating, reviewing, or merging pull requests through mai. Git-native PRs stored as notes — no GitHub, no Forgejo, no platform lock-in. Covers creation, review (accept/reject), submission (merge), auto-close, and diff inspection.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | mai-pr |
| description | Use when creating, reviewing, or merging pull requests through mai. Git-native PRs stored as notes — no GitHub, no Forgejo, no platform lock-in. Covers creation, review (accept/reject), submission (merge), auto-close, and diff inspection. |
PRs in maitake are kind: pr notes with source and target branches in targets[]. Everything lives in refs/notes/maitake — syncs with git push/pull, merges via set-union.
# On a feature branch:
git checkout -b feature/auth
# ... make changes, commit ...
mai pr "Add auth middleware" --into main
# → mai-5c4a feature/auth → main
mai pr # list open PRs
mai pr show mai-5c4a # details + diff summary + review status
mai pr diff mai-5c4a # full diff
mai pr accept mai-5c4a # LGTM
mai pr submit mai-5c4a # merge + close
mai pr "title" --into <target> # target defaults to main
mai pr "title" -d "description" # with body
mai pr "title" -a reviewer # assign reviewer
mai pr "title" -l auth,backend # add tags
The source branch is auto-detected from HEAD. Fails on detached HEAD or if source equals target.
If no title is given, auto-generates feature/auth → main.
mai pr # all PRs (open, closed, merged)
mai pr --json # JSON output
Auto-close: When listing, any PR whose source branch is already merged into the target gets automatically closed with a comment.
mai pr show <id> # details + diff summary + review verdict + comments
mai pr show <id> --diff # include full inline diff
mai pr show <id> --json # JSON output
The show output includes:
--stat style)mai pr accept <id> # default message: "LGTM"
mai pr accept <id> -m "Ship it" # custom message
Appends a comment with resolved: true.
mai pr reject <id> -m "Race condition in token refresh"
Appends a comment with resolved: false. Message is required.
Accept and reject stack — the latest resolved comment determines the verdict. Multiple reviewers can all leave accept/reject comments; pr show displays all of them.
mai pr accept <id> -m "LGTM from auth team"
mai pr reject <id> -m "Needs perf testing" # overrides to rejected
mai pr accept <id> -m "Perf tested, all good" # back to accepted
mai pr comment <id> -m "Looks good overall"
mai pr comment <id> -m "Race here" --file src/auth.ts --line 42
Same as mai add-note but scoped to the PR. Supports file-located and line-located comments.
Long comments — use the pipe pattern. Write to
/tmpfirst, pipe in. (See mai-agent skill.)
mai pr diff <id> # full diff (target...source)
mai pr diff <id> --stat # summary only
mai pr submit <id> # merge source into target, close the PR
mai pr submit <id> --force # skip unresolved comment check
Submit does:
--force)git checkout <target> && git merge <source> (no-ff)If the source branch was merged outside of mai (via git merge, GitHub, etc.), submit detects it and just closes the note.
git checkout -b feature/auth
# implement...
git commit -m "Add auth middleware"
mai pr "Add auth middleware" --into main -a reviewer
mai pr show <id> # reviewer reads the PR
mai pr diff <id> # reviewer checks the diff
mai pr comment <id> -m "Missing null check" --file src/auth.ts --line 15
mai pr reject <id> -m "See inline comments"
# implementer fixes...
git commit -m "Fix null check"
mai pr accept <id> -m "Fixed, LGTM"
mai pr submit <id>
# → Merged feature/auth into main. mai-5c4a → closed.
A PR is a note with:
kind: "pr"targets: [sourceBranch, targetBranch]resolved: true/false) and discussionAccept = comment with resolved: true
Reject = comment with resolved: false
Submit = git merge + close event
Auto-close = close event triggered by merge detection
| Scenario | Result |
|---|---|
| Detached HEAD | fatal: pr: not on a branch |
| Source = target | fatal: pr: source and target are the same branch |
pr show on a ticket | fatal: pr show: <id> is not a PR (kind: ticket) |
pr reject without -m | fatal: pr reject: reason required |
pr submit with unresolved comments | fatal: pr submit: unresolved comments exist (use --force) |
pr submit on closed PR | fatal: pr submit: <id> is already closed |
| Merge conflict during submit | fatal: pr submit: merge failed: <git error> |
cmd/mai/pr.go — all PR subcommandscmd/mai/main.go — dispatchPR routing + withEngineAndRepo helpertest/pr_test.go — 29 regression testspkg/notes/engine.go — IsMerged, GitBranchpkg/git/git.go — IsAncestor, Diff, MergeBase, MergeRefUse when a repo needs durable mai-backed context so every agent sees rules, rationale, and hazards before editing code. Covers promoting chat knowledge into tickets, constraints, warnings, ADRs, artifacts, and reviews; mirroring critical items into AGENTS.md; and enforcing mai context usage through arrival rituals, delegation templates, review gates, and verification.
Use when recording architecture decisions (ADRs). Decisions are kind:decision notes attached to code via --target, queryable via mai ls/context, and optionally materialize as markdown files. Covers detection triggers, tier system, comment templates, and anti-patterns.
Use when working in any git repo with maitake. Check for notes before touching files, leave notes after meaningful work. This is the base agent contract — all other mai skills build on it.
Use when setting or checking project rules that all agents must follow. Constraints show up in mai context alongside tickets and warnings. They stay open until the rule changes.
Use when coordinating work across multiple agents via teams. Create tickets, delegate, track deps, monitor progress, run reviews — all through mai.
Use when conducting research, oracle investigations, or delphi consultations. Save findings as mai notes with proper tags and structure.