메뉴
Commit changes using sase commit for Google's fig VCS. This skill is the ONLY way that you should EVER commit to fig repos. NEVER invoke this skill unless the user explicitly asks you to commit or a post-completion finalizer triggers it.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Report on currently-running SASE agents. Use when the user asks "what's running?", "agent status", "status report", or any question about live/background agents.
Reference for sase bead commands (create, update, list, search, ready, show, dep). Use when working with beads.
Inspect prior sase agent chat transcripts. Use when the user asks about previous chats, chat transcripts, prior agent conversations, "what did agent X say?", "summarize the previous agent", or any question about an earlier sase agent's prompt or response.
Create an implementation plan. Use instead of plan mode (which is disabled).
Create an implementation plan. Use instead of plan mode (which is disabled).
Create an implementation plan. Use instead of plan mode (which is disabled).
| name | sase_hg_commit |
| description | Commit changes using sase commit for Google's fig VCS. This skill is the ONLY way that you should EVER commit to fig repos. NEVER invoke this skill unless the user explicitly asks you to commit or a post-completion finalizer triggers it. |
Before doing anything else, run this command to record that you are using this skill:
sase skill use sase_hg_commit --reason "<one-line reason for using this skill>"
Commit changes via the sase commit command.
Examine uncommitted changes — Run hg status or hg diff to understand what files have changed and why.
Write a commit message file — Create a file (e.g., commit_message.md) containing a good commit message.
Run the commit — Execute:
sase commit -M commit_message.md -f file1.py -f file2.py
Flags:
-M: Path to file containing the commit message. The file is deleted after reading.-m: Inline commit message string (alternative to -M). -m and -M are mutually exclusive.-f: File to include (repeat for multiple files). Omit to include all changes.--name: CL name (only needed for create_pull_request method).The $SASE_COMMIT_METHOD environment variable is read automatically to determine the dispatch method
(create_commit, create_proposal, or create_pull_request). Do NOT pass --type unless you need to override.
sase commit -M commit_message.md -f auth.py -f login.py
If sase commit exits with code 2 and prints a "merge conflict" message, the local repository is in a paused
evolve/rebase state and the post-commit bookkeeping has been deferred. Do NOT re-run the original sase commit command.
Instead, resolve the conflict and finalize:
hg resolve --list (lines starting with U are unresolved).hg resolve --mark <file> for each.hg rebase --continue (or hg evolve --continue). Repeat steps 1–4 until clean.hg status should be empty.sase commit --resume.