[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CCFMFV3BPFRFGARP5S7V15":3,"skill-same:01M6CCFMFV3BPFRFGARP5S7V15":72},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":55,"ownerDescription":57,"updatedAt":58,"install":59,"resources":71},"01M6CCFMFV3BPFRFGARP5S7V15","create-stigmer-oss-pull-request",null,"Writes a pull request title and description from the branch's commits and diff, then pushes the branch and opens the pull request with the GitHub CLI. Invoke by name to open a PR, or to draft only the title and body without opening one.","stigmer\u002Fstigmer","stigmer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255479904?v=4","01M6CCFBFXXRZC4ZVNS3JSDV4W","Stigmer","01M6CCFBKY7M8QGR4GH9TT35MY",9,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-stigmer-oss-pull-request\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"request","pull request","create","pull","oss","create stigmer oss pull request","only","title","true","with","github cli","name","draft","cli","diff","branch","commits","open","pr","github","2026-11-10 10:12:30",false,"---\nname: create-stigmer-oss-pull-request\ndescription:\n  Writes a pull request title and description from the branch's commits and\n  diff, then pushes the branch and opens the pull request with the GitHub CLI.\n  Invoke by name to open a PR, or to draft only the title and body without\n  opening one.\ndisable-model-invocation: true\n---\n\n# Create a Stigmer OSS pull request\n\nTwo modes, one procedure. Asked for the title and body only, produce the two\nblocks below and change nothing. Asked to open the PR, produce them, push, and\nrun `gh pr create` from the worktree, non-interactively; if a prerequisite is\nmissing (`gh` not installed or not authenticated), stop with the command that\nfixes it.\n\n## Preconditions\n\n- The branch already exists: work happens in a git worktree that owns it, so\n  there is no branch to create here. Commits come from\n  `.agents\u002Fskills\u002Fcommit-stigmer-oss-changes\u002FSKILL.md`; uncommitted changes are\n  committed there first or left out deliberately.\n- `gh auth status` succeeds and `origin` is writable.\n- Base branch: `gh repo view --json defaultBranchRef -q .defaultBranchRef.name`,\n  falling back to `main`.\n- One pull request per branch. If `gh pr list --head \u003Cbranch>` finds one, push\n  and stop; never open a second.\n- The change was written and verified under `.agents\u002Fskills\u002Ftest-gate\u002FSKILL.md`;\n  load it now if it is not already loaded, and answer its questions before\n  \"done\" before writing the test plan.\n\n## Read the branch before writing\n\n```bash\ngit log --oneline origin\u002Fmain..HEAD\ngit diff --name-status origin\u002Fmain...HEAD\ngit diff --stat origin\u002Fmain...HEAD\n```\n\nThe commits say what changed and why; the file list decides the scope.\n\n## The title\n\nOne line, in a fenced `text` block when drafting:\n\n```text\n\u003Ctype>(\u003Cscope>): \u003Cimperative summary>\n```\n\n`\u003Ctype>` is one of `feat`, `fix`, `refactor`, `docs`, `test`, `perf`, `ci`,\n`build`, `chore`, `revert`; `\u003Cscope>` follows the scope rule in the commit skill\n(the most affected area from the repository map, path-like, `repo` for\nrepository-wide changes); the summary is imperative, specific, at most 72\ncharacters after the prefix, no trailing period.\n\n## The body\n\nA fenced `markdown` block when drafting. Use the sections that apply and omit\nthe rest:\n\n```markdown\n## Summary\n\n\u003Cone to three sentences in plain language>\n\n## Context\n\n\u003Cthe problem, bug or goal that made the change necessary>\n\n## Changes\n\n- \u003Ckey change, grouped by area when several>\n\n## Implementation notes\n\n- \u003Ca decision or trade-off a reviewer should know>\n\n## Breaking changes\n\n- \u003Cwhat breaks and how to migrate, or \"None\">\n\n## Test plan\n\n- \u003Cthe checks that ran, with their summary lines; manual steps; screenshots>\n\n## Risks\n\n- \u003Cwhat could go wrong and how to roll back>\n\nCloses #\u003Cissue>\n```\n\nThe test plan quotes evidence, not intentions: the summary line of each check\nthat ran, as the root guide's verification map asks. A PR that fixes an issue\ncarries `Closes #N` in the body, where it survives a squash merge.\n\nNo body promises a check to be read after the next release. A clause is proven\nby a test, or dropped. What only a released build can show becomes one of the\nrelease's own checks, added by this PR to the release workflow that publishes\nthe thing (`.agents\u002Fskills\u002Frelease-stigmer-oss\u002FSKILL.md` names each), so every\nrelease reads it again.\n\nNothing merges into `main` but through the checks its ruleset requires: `Gate`\nand `Test integrity` on the pull request, and, while the ruleset says so,\n`Review verdict` and a merge queue that runs `Gate` and `Test integrity` again\non the queue's commit. When a review is needed, and what a verdict is, is in\n`.agents\u002Fskills\u002Freview-pull-request\u002FSKILL.md` (\"When a review is needed\"); a\nverdict is a comment, never a section of this body. The merge arms\n`gh pr merge \u003Cn> --auto` (with `--squash` when the brief's ruleset read gives\n`queue: false`) and hands back; nobody waits. The local checks the test plan\nquotes still come first, because a red `Gate` costs a round trip.\n\n## Opening it\n\n```bash\ngit push -u origin \"$(git branch --show-current)\"\ngh pr create --title \"$TITLE\" --body \"$BODY\" [--draft] [--reviewer ...] [--label ...]\n```\n\nOne PR per milestone, opened once the milestone is built and verified locally.\nBefore that the branch is pushed with no PR, which runs no CI, and a fix found\nwhile building rides the milestone's PR unless another change needs it on `main`\nnow. A PR per project would hold its work off `main` for days, drift against\nevery other merge, and expose more lanes to each flaky test in the queue. Open a\ndraft only when the owner asks to see the work early; a draft is reviewed when\nit is marked ready. Once the pull request is open and its local checks pass, run\n`.agents\u002Fskills\u002Freview-pull-request\u002FSKILL.md` when its \"When a review is needed\"\nsection says to, and act on the verdict as it says. Report the PR URL and any\nverdict. Merging is a separate, explicitly requested act, never part of opening.\n","# Create a Stigmer OSS pull request\n\nTwo modes, one procedure. Asked for the title and body only, produce the two\nblocks below and change nothing. Asked to open the PR, produce them, push, and\nrun `gh pr create` from the worktree, non-interactively; if a prerequisite is\nmissing (`gh` not installed or not authenticated), stop with the command that\nfixes it.\n\n## Preconditions\n\n- The branch already exists: work happens in a git worktree that owns it, so\n  there is no branch to create here. Commits come from\n  `.agents\u002Fskills\u002Fcommit-stigmer-oss-changes\u002FSKILL.md`; uncommitted changes are\n  committed there first or left out deliberately.\n- `gh auth status` succeeds and `origin` is writable.\n- Base branch: `gh repo view --json defaultBranchRef -q .defaultBranchRef.name`,\n  falling back to `main`.\n- One pull request per branch. If `gh pr list --head \u003Cbranch>` finds one, push\n  and stop; never open a second.\n- The change was written and verified under `.agents\u002Fskills\u002Ftest-gate\u002FSKILL.md`;\n  load it now if it is not already loaded, and answer its questions before\n  \"done\" before writing the test plan.\n\n## Read the branch before writing\n\n```bash\ngit log --oneline origin\u002Fmain..HEAD\ngit diff --name-status origin\u002Fmain...HEAD\ngit diff --stat origin\u002Fmain...HEAD\n```\n\nThe commits say what changed and why; the file list decides the scope.\n\n## The title\n\nOne line, in a fenced `text` block when drafting:\n\n```text\n\u003Ctype>(\u003Cscope>): \u003Cimperative summary>\n```\n\n`\u003Ctype>` is one of `feat`, `fix`, `refactor`, `docs`, `test`, `perf`, `ci`,\n`build`, `chore`, `revert`; `\u003Cscope>` follows the scope rule in the commit skill\n(the most affected area from the repository map, path-like, `repo` for\nrepository-wide changes); the summary is imperative, specific, at most 72\ncharacters after the prefix, no trailing period.\n\n## The body\n\nA fenced `markdown` block when drafting. Use the sections that apply and omit\nthe rest:\n\n```markdown\n## Summary\n\n\u003Cone to three sentences in plain language>\n\n## Context\n\n\u003Cthe problem, bug or goal that made the change necessary>\n\n## Changes\n\n- \u003Ckey change, grouped by area when several>\n\n## Implementation notes\n\n- \u003Ca decision or trade-off a reviewer should know>\n\n## Breaking changes\n\n- \u003Cwhat breaks and how to migrate, or \"None\">\n\n## Test plan\n\n- \u003Cthe checks that ran, with their summary lines; manual steps; screenshots>\n\n## Risks\n\n- \u003Cwhat could go wrong and how to roll back>\n\nCloses #\u003Cissue>\n```\n\nThe test plan quotes evidence, not intentions: the summary line of each check\nthat ran, as the root guide's verification map asks. A PR that fixes an issue\ncarries `Closes #N` in the body, where it survives a squash merge.\n\nNo body promises a check to be read after the next release. A clause is proven\nby a test, or dropped. What only a released build can show becomes one of the\nrelease's own checks, added by this PR to the release workflow that publishes\nthe thing (`.agents\u002Fskills\u002Frelease-stigmer-oss\u002FSKILL.md` names each), so every\nrelease reads it again.\n\nNothing merges into `main` but through the checks its ruleset requires: `Gate`\nand `Test integrity` on the pull request, and, while the ruleset says so,\n`Review verdict` and a merge queue that runs `Gate` and `Test integrity` again\non the queue's commit. When a review is needed, and what a verdict is, is in\n`.agents\u002Fskills\u002Freview-pull-request\u002FSKILL.md` (\"When a review is needed\"); a\nverdict is a comment, never a section of this body. The merge arms\n`gh pr merge \u003Cn> --auto` (with `--squash` when the brief's ruleset read gives\n`queue: false`) and hands back; nobody waits. The local checks the test plan\nquotes still come first, because a red `Gate` costs a round trip.\n\n## Opening it\n\n```bash\ngit push -u origin \"$(git branch --show-current)\"\ngh pr create --title \"$TITLE\" --body \"$BODY\" [--draft] [--reviewer ...] [--label ...]\n```\n\nOne PR per milestone, opened once the milestone is built and verified locally.\nBefore that the branch is pushed with no PR, which runs no CI, and a fix found\nwhile building rides the milestone's PR unless another change needs it on `main`\nnow. A PR per project would hold its work off `main` for days, drift against\nevery other merge, and expose more lanes to each flaky test in the queue. Open a\ndraft only when the owner asks to see the work early; a draft is reviewed when\nit is marked ready. Once the pull request is open and its local checks pass, run\n`.agents\u002Fskills\u002Freview-pull-request\u002FSKILL.md` when its \"When a review is needed\"\nsection says to, and act on the verdict as it says. Report the PR URL and any\nverdict. Merging is a separate, explicitly requested act, never part of opening.\n",{"name":5,"description":7,"disable-model-invocation":49},true,"main","7b43d462fc7be62a629567ceaecfed197c8a1c1b",".agents\u002Fskills\u002Fcreate-stigmer-oss-pull-request",6,"https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer","https:\u002F\u002Fstigmer.ai","https:\u002F\u002Fgithub.com\u002Fstigmer","The open-source backend for the agents in your product.","2026-11-14 02:41:36",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":49},[61,64,67],{"tool":62,"command":63},"npx","npx skills add stigmer\u002Fstigmer --skill create-stigmer-oss-pull-request",{"tool":65,"command":66},"bunx","bunx skills add stigmer\u002Fstigmer --skill create-stigmer-oss-pull-request",{"tool":68,"command":69},"pnpm","pnpm dlx skills add stigmer\u002Fstigmer --skill create-stigmer-oss-pull-request","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-stigmer-oss-pull-request\u002FSKILL.md",[],[73,100,120,138,152,168],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":90,"publishedAt":44},"01M6CCSERKR4YRSZJ2TB6B0X60","writing-hookify-rules","This skill should be used when the user asks to \"create a hookify rule\", \"write a hook rule\", \"configure hookify\", \"add a hookify rule\", or needs guidance on hookify rule syntax and patterns.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fsupport\u002Ffixtures\u002Fclaude-plugins\u002Fhookify\u002Fskills\u002Fwriting-rules\u002FSKILL.md",[79,82,85],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[91,92,93,94,26,95,96,97,98,99],"writing","Writing Hookify Rules","Rules","hookify rules","guidance","user","write","configure","syntax",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":112,"publishedAt":44},"01M6CCSC63RKCGC2S1EZDEMXZE","sql-migrations","Write safe database schema migrations - reversible steps, online index builds, and backfills in batches.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fsql-migrations\u002FSKILL.md",[106,109],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":110,"categoryName":111,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000033","数据分析师",[113,114,115,116,97,117,118,119],"sql","sql migrations","migrations","schema","index","database","safe",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":44},"01M6CCS9Q8E0R3TYHPZHCPN0JZ","repo-conventions","How to change Go code in this repository - error wrapping, table-driven tests, doc comments, no new dependencies, and running go test before finishing.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Frepo-conventions\u002FSKILL.md",[],[127,128,129,130,131,132,133,134,135,136,137],"repo","repo conventions","table","go","test","change","doc comments","code","repository","doc","how",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":44},"01M6CCS7F2D1YZ9H3N63XTEV09","incident-postmortem","Write a blameless incident postmortem - timeline, impact, root cause, contributing factors and follow-up actions with owners.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fincident-postmortem\u002FSKILL.md",[],[145,146,97,147,148,149,150,151],"incident postmortem","postmortem","contributing","actions","timeline","owners","up",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":162,"publishedAt":44},"01M6CCS4W1D2K257KHC40HS8JG","data-analysis","Summarise a data export or table - lead with the key finding and give every number its baseline or comparison.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fdata-analysis\u002FSKILL.md",[158,161],{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":110,"categoryName":111,"taxonomyType":88,"taxonomyTypeDesc":89},[163,164,165,166,129,167],"analysis","data analysis","data","baseline","export",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":44},"01M6CCS2MNQYK9S24AYHJAVPWF","customer-support","Answer customer questions about orders, returns and refunds from the written policies and the order system, ending with a clear next step.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fcustomer-support\u002FSKILL.md",[],[175,176,177,178,179,180],"support","customer","customer support","system","refunds","returns"]