[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77NH76B652M06AH84WNS2YX":3,"skill-same:01M77NH76B652M06AH84WNS2YX":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M77NH76B652M06AH84WNS2YX","ce-commit",null,"Create a local Jujutsu commit with a clear, value-communicating message. Use when the user asks to commit\u002Fsave selected working-copy changes with a repo-appropriate message.","ucirello\u002Fcompound-engineering-plugin","ucirello","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F138827?v=4","01M77NFWYZ15SBS6EHVHBDDNA6","U Cirello","01M77NFWZJS5P3EKSVVKR8K5G9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-commit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ce-commit\ndescription: Create a local Jujutsu commit with a clear, value-communicating message. Use when the user asks to commit\u002Fsave selected working-copy changes with a repo-appropriate message.\n---\n\n# Jujutsu Commit\n\nCreate well-crafted local commit(s) from the current working copy. No push, no PR — use `ce-commit-push-pr` for the full ship flow.\n\n**Done when:** each logical change is committed with an explicit file list and a message that states the outcome, and `jj status` shows those changes no longer pending. **Stop when:** there are no changes to commit.\n\n## Context\n\nDiscover the absolute workspace root with `jj workspace root`. Run every subsequent JJ command with the shell tool's working directory set to that absolute root, not merely with `jj -R`. Each command is its own shell call (program + args); interpret non-zero exits rather than suppressing them. Never invoke the Git executable, including for history or index inspection. JJ has no staging index: existing Git staging is not a selection mechanism.\n\n| Command | Purpose | Non-zero \u002F empty means |\n| --- | --- | --- |\n| `jj status` | Working-copy changes, conflicts and untracked-file warnings | Not a JJ workspace — stop |\n| `jj diff --summary` | Changed paths in `@` | Empty may mean nothing to commit; also inspect status warnings |\n| `jj log --no-graph -r '@ | @-'` | Current change and parent identities | Resolve errors before continuing |\n| `jj bookmark list` | Local and remote bookmark targets | No bookmarks is valid |\n| `jj git remote list` | Configured remotes | No remote is valid for local commits |\n\nResolve the actual task history head from the verified current change, its parent(s), and any task-specified bookmark or revision. An empty `@` may sit above the relevant history. Do not assume a default-branch name or silently replace the task's anchor. If the default branch matters, inspect repository configuration or query `gh repo view --json defaultBranchRef` with `GIT_DIR` set to the value obtained by `jj git root` in this absolute workspace root. If it cannot be established, report that ambiguity rather than guessing.\n\nTreat this as a snapshot. Re-read status, identities and selected paths immediately before committing if anything may have changed. Stop on conflicts or ambiguous scope; preserve unrelated work.\n\n## Message standards\n\n**Based on https:\u002F\u002Fgo.dev\u002Fwiki\u002FCommitMessage and on past commit messages that you can see in `jj log`, compose commit messages adherent to the present standards.**\n\nBefore composing, read the **full** https:\u002F\u002Fgo.dev\u002Fwiki\u002FCommitMessage at runtime. From the target workspace's absolute root, inspect several recent complete subjects **and bodies** at the verified task history head:\n\n```bash\njj log --no-graph -r '::\u003Cverified-history-head>' -n 10 -T 'description ++ \"\\n\"'\n```\n\nCompare prefixes\u002Fpackage names, casing, verb tense, subject\u002Fbody separation, wrapping, and issue-reference placement across several commits. Repository-local syntax established by project\u002Fuser instructions and that history **always wins** over differing Go guidance. Apply compatible Go guidance to clarity, quality and structure within the observed pattern; do not impose a fixed prefix, type, scope or template. With no history, use explicit project\u002Fuser instructions and Go guidance without inventing a repository precedent.\n\n### Verbatim Go source guidance — illustrative, not a repository template\n\n> Commit messages, also known as CL (changelist) descriptions, should be formatted per https:\u002F\u002Fgo.dev\u002Fdoc\u002Fcontribute#commit_messages. For example,\n\n```text\nnet\u002Fhttp: handle foo when bar\n\n[longer description here in the body]\n\nFixes #12345\n```\n\n> Notably, for the subject (the first line of description):\n> - the name of the package affected by the change goes before the colon\n> - the part after the colon uses the verb tense + phrase that completes the blank in, “this change modifies Go to **___**”\n> - the verb after the colon is lowercase\n> - there is no trailing period\n> - it should be kept as short as possible (many git viewing tools prefer under ~72 characters, though Go isn’t super strict about this).\n\n> For the body (the rest of the description):\n> - the text should be wrapped to ~72 characters (to appease git viewing tools, mainly), unless you really need longer lines (e.g. for ASCII art, tables, or long links).\n> - the Fixes line goes after the body with a blank newline separating the two. (It is acceptable but not required to use a trailing period, such as Fixes #12345.).\n> - there is no Markdown in the commit message.\n> - similarly, we do not use Co-authored-by and Assisted-by lines. Don’t add them.\n\n## Workflow\n\n0. **Gather** — run the Context commands, resolve the history anchor, and read and compare the message standards above.\n\n1. **Nothing to commit** — if status and diff show no pending changes or untracked files to include, report that and stop. Do not mistake ignored or untracked-file warnings for committed content.\n\n2. **Bookmark first** — JJ changes do not have detached HEAD. If the work has no task bookmark, or its bookmark is the verified default branch, create a non-conflicting feature bookmark derived from the change content at `@` using `jj bookmark create \u003Cname> -r @`, then verify its target. Do not move the default bookmark. If a name exists, choose a non-conflicting suffix. Preserve existing task\u002Fsource bookmarks.\n\n3. **Convention** — determine syntax at runtime using Message standards; do not select a fallback Conventional Commit template.\n\n4. **Logical commits** — if changed files clearly split into distinct concerns, make separate commits (file level only, 2–3 max, no interactive patch selection). If ambiguous, one commit.\n\n5. **Message** — communicate the outcome rather than merely listing files. Include motivation or trade-offs when needed. When an Implementation Unit ID is already in hand and this commit belongs to that single unit, include that ID in the repository-compatible form; do not hunt for a plan. Omit it when spanning units or when unclear. Preserve human authorship credit for ported branch\u002FPR\u002Fpatch work: copy recorded names and identities exactly, never guess an email. Follow repository-local credit requirements when present; otherwise acknowledge those humans in the body consistently with the Go guidance. Do not add assistant\u002Fmodel\u002Fharness attribution.\n\n6. **Commit named files only** — honor `exclude:\u003Cpaths>`: those paths remain uncommitted and must be mentioned in the report. Use root-relative explicit file paths (not workspace-prefixed paths), including deleted paths; do not use a broad directory or whole-tree selection. If an intended untracked file is not tracked, use `jj file track \u003Cexact-path>` only for that authorized file and verify selection again. Never force-track ignored content without authorization.\n\n   Supply the full dynamically composed message as a single literal argument through the shell tool's program\u002Fargument interface, without interpolating message text into shell source:\n\n```bash\njj commit -m \"\u003Cmessage composed from the standards above>\" -- file1 file2 file3\n```\n\n   JJ commits the selected paths in `@` and moves the remaining changes to a new working-copy child. The explicit path list is required: omitting it would include unrelated or excluded changes. No index staging or Git commit command is needed. If a tool requires a message artifact, keep it under the absolute workspace root's `.tmp\u002F`, ensure `.tmp\u002F` is ignored, and read it literally rather than evaluating its contents.\n\n   Record the committed revision after each group and verify the feature bookmark still targets the intended committed work. `jj commit` does not move bookmarks to its new child: for subsequent groups move only this task's feature bookmark to the verified selected working-copy change before committing, leaving other bookmarks untouched.\n\n7. **Confirm** — run `jj status`, inspect the committed revisions and their complete descriptions, and report commit IDs and subjects. Verify only selected files were included and excluded\u002Funrelated changes remain pending. An empty working-copy child is normal, not an additional commit to publish.\n\nJJ operation references: https:\u002F\u002Fdocs.jj-vcs.dev\u002Flatest\u002Fcli-reference\u002F and https:\u002F\u002Fdocs.jj-vcs.dev\u002Flatest\u002Fgit-command-table\u002F.\n","# Jujutsu Commit\n\nCreate well-crafted local commit(s) from the current working copy. No push, no PR — use `ce-commit-push-pr` for the full ship flow.\n\n**Done when:** each logical change is committed with an explicit file list and a message that states the outcome, and `jj status` shows those changes no longer pending. **Stop when:** there are no changes to commit.\n\n## Context\n\nDiscover the absolute workspace root with `jj workspace root`. Run every subsequent JJ command with the shell tool's working directory set to that absolute root, not merely with `jj -R`. Each command is its own shell call (program + args); interpret non-zero exits rather than suppressing them. Never invoke the Git executable, including for history or index inspection. JJ has no staging index: existing Git staging is not a selection mechanism.\n\n| Command | Purpose | Non-zero \u002F empty means |\n| --- | --- | --- |\n| `jj status` | Working-copy changes, conflicts and untracked-file warnings | Not a JJ workspace — stop |\n| `jj diff --summary` | Changed paths in `@` | Empty may mean nothing to commit; also inspect status warnings |\n| `jj log --no-graph -r '@ | @-'` | Current change and parent identities | Resolve errors before continuing |\n| `jj bookmark list` | Local and remote bookmark targets | No bookmarks is valid |\n| `jj git remote list` | Configured remotes | No remote is valid for local commits |\n\nResolve the actual task history head from the verified current change, its parent(s), and any task-specified bookmark or revision. An empty `@` may sit above the relevant history. Do not assume a default-branch name or silently replace the task's anchor. If the default branch matters, inspect repository configuration or query `gh repo view --json defaultBranchRef` with `GIT_DIR` set to the value obtained by `jj git root` in this absolute workspace root. If it cannot be established, report that ambiguity rather than guessing.\n\nTreat this as a snapshot. Re-read status, identities and selected paths immediately before committing if anything may have changed. Stop on conflicts or ambiguous scope; preserve unrelated work.\n\n## Message standards\n\n**Based on https:\u002F\u002Fgo.dev\u002Fwiki\u002FCommitMessage and on past commit messages that you can see in `jj log`, compose commit messages adherent to the present standards.**\n\nBefore composing, read the **full** https:\u002F\u002Fgo.dev\u002Fwiki\u002FCommitMessage at runtime. From the target workspace's absolute root, inspect several recent complete subjects **and bodies** at the verified task history head:\n\n```bash\njj log --no-graph -r '::\u003Cverified-history-head>' -n 10 -T 'description ++ \"\\n\"'\n```\n\nCompare prefixes\u002Fpackage names, casing, verb tense, subject\u002Fbody separation, wrapping, and issue-reference placement across several commits. Repository-local syntax established by project\u002Fuser instructions and that history **always wins** over differing Go guidance. Apply compatible Go guidance to clarity, quality and structure within the observed pattern; do not impose a fixed prefix, type, scope or template. With no history, use explicit project\u002Fuser instructions and Go guidance without inventing a repository precedent.\n\n### Verbatim Go source guidance — illustrative, not a repository template\n\n> Commit messages, also known as CL (changelist) descriptions, should be formatted per https:\u002F\u002Fgo.dev\u002Fdoc\u002Fcontribute#commit_messages. For example,\n\n```text\nnet\u002Fhttp: handle foo when bar\n\n[longer description here in the body]\n\nFixes #12345\n```\n\n> Notably, for the subject (the first line of description):\n> - the name of the package affected by the change goes before the colon\n> - the part after the colon uses the verb tense + phrase that completes the blank in, “this change modifies Go to **___**”\n> - the verb after the colon is lowercase\n> - there is no trailing period\n> - it should be kept as short as possible (many git viewing tools prefer under ~72 characters, though Go isn’t super strict about this).\n\n> For the body (the rest of the description):\n> - the text should be wrapped to ~72 characters (to appease git viewing tools, mainly), unless you really need longer lines (e.g. for ASCII art, tables, or long links).\n> - the Fixes line goes after the body with a blank newline separating the two. (It is acceptable but not required to use a trailing period, such as Fixes #12345.).\n> - there is no Markdown in the commit message.\n> - similarly, we do not use Co-authored-by and Assisted-by lines. Don’t add them.\n\n## Workflow\n\n0. **Gather** — run the Context commands, resolve the history anchor, and read and compare the message standards above.\n\n1. **Nothing to commit** — if status and diff show no pending changes or untracked files to include, report that and stop. Do not mistake ignored or untracked-file warnings for committed content.\n\n2. **Bookmark first** — JJ changes do not have detached HEAD. If the work has no task bookmark, or its bookmark is the verified default branch, create a non-conflicting feature bookmark derived from the change content at `@` using `jj bookmark create \u003Cname> -r @`, then verify its target. Do not move the default bookmark. If a name exists, choose a non-conflicting suffix. Preserve existing task\u002Fsource bookmarks.\n\n3. **Convention** — determine syntax at runtime using Message standards; do not select a fallback Conventional Commit template.\n\n4. **Logical commits** — if changed files clearly split into distinct concerns, make separate commits (file level only, 2–3 max, no interactive patch selection). If ambiguous, one commit.\n\n5. **Message** — communicate the outcome rather than merely listing files. Include motivation or trade-offs when needed. When an Implementation Unit ID is already in hand and this commit belongs to that single unit, include that ID in the repository-compatible form; do not hunt for a plan. Omit it when spanning units or when unclear. Preserve human authorship credit for ported branch\u002FPR\u002Fpatch work: copy recorded names and identities exactly, never guess an email. Follow repository-local credit requirements when present; otherwise acknowledge those humans in the body consistently with the Go guidance. Do not add assistant\u002Fmodel\u002Fharness attribution.\n\n6. **Commit named files only** — honor `exclude:\u003Cpaths>`: those paths remain uncommitted and must be mentioned in the report. Use root-relative explicit file paths (not workspace-prefixed paths), including deleted paths; do not use a broad directory or whole-tree selection. If an intended untracked file is not tracked, use `jj file track \u003Cexact-path>` only for that authorized file and verify selection again. Never force-track ignored content without authorization.\n\n   Supply the full dynamically composed message as a single literal argument through the shell tool's program\u002Fargument interface, without interpolating message text into shell source:\n\n```bash\njj commit -m \"\u003Cmessage composed from the standards above>\" -- file1 file2 file3\n```\n\n   JJ commits the selected paths in `@` and moves the remaining changes to a new working-copy child. The explicit path list is required: omitting it would include unrelated or excluded changes. No index staging or Git commit command is needed. If a tool requires a message artifact, keep it under the absolute workspace root's `.tmp\u002F`, ensure `.tmp\u002F` is ignored, and read it literally rather than evaluating its contents.\n\n   Record the committed revision after each group and verify the feature bookmark still targets the intended committed work. `jj commit` does not move bookmarks to its new child: for subsequent groups move only this task's feature bookmark to the verified selected working-copy change before committing, leaving other bookmarks untouched.\n\n7. **Confirm** — run `jj status`, inspect the committed revisions and their complete descriptions, and report commit IDs and subjects. Verify only selected files were included and excluded\u002Funrelated changes remain pending. An empty working-copy child is normal, not an additional commit to publish.\n\nJJ operation references: https:\u002F\u002Fdocs.jj-vcs.dev\u002Flatest\u002Fcli-reference\u002F and https:\u002F\u002Fdocs.jj-vcs.dev\u002Flatest\u002Fgit-command-table\u002F.\n",{"name":5,"description":7},"main","03ecf78d3885acd7cbd6ff9f37928d306cc7ba0e","skills\u002Fce-commit","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin","https:\u002F\u002Fgithub.com\u002Fucirello","Gopher. Mars aficionado.","2026-11-14 06:10:50",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add ucirello\u002Fcompound-engineering-plugin --skill ce-commit",{"tool":37,"command":38},"bunx","bunx skills add ucirello\u002Fcompound-engineering-plugin --skill ce-commit",{"tool":40,"command":41},"pnpm","pnpm dlx skills add ucirello\u002Fcompound-engineering-plugin --skill ce-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-commit\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M78VM0YXEHCKHF8YT1P2WFHF","ce-retro","Look back over an agent session in this repo, the current one by default or any scope the user names across harnesses, and find what in the repo's environment keeps costing agents effort or leading them into mistakes, keeping only fixes the evidence shows are worth it. Lands the approved environment fixes and hands the rest to their owners. Use for a retro, postmortem, or papercut sweep of how agents worked in this repo. Use ce-compound to keep the lesson of one solved problem, and ce-debug for a bug in product code.","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Fskills\u002Fce-retro\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77NMFCKBMKN3C8EACVGP8TG","release-notes","Draft release notes from merged pull requests since the last tag. Use when preparing a release.","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Ftests\u002Fskill-eval-cell\u002Ffixtures\u002Freview-roster-skill-prose\u002Fskills\u002Frelease-notes\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77NMEKMA0BXHC4230FV7S39","skill-one","Sample skill","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fskill-one\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77NMCCVPH1F4P94W3CCAP5T","disabled-skill","A skill with model invocation disabled","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fdisabled-skill\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77NMACM3ACB6PX92GMHFF3P","claude-only-skill","A skill restricted to Claude Code only","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fclaude-only-skill\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77NM9ACPBEWHX6Z3QT1PRMS","agent-only-skill","An agent-only skill not intended for direct user invocation","https:\u002F\u002Fgithub.com\u002Fucirello\u002Fcompound-engineering-plugin\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsample-plugin\u002Fskills\u002Fagent-only-skill\u002FSKILL.md",[],[]]