[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACGAP25ER09HE3H2FJ9DJA":3,"skill-same:01M6ACGAP25ER09HE3H2FJ9DJA":98},{"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":26,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6ACGAP25ER09HE3H2FJ9DJA","tinker-merge",null,"Merge work forward through Apache TinkerPop's release branches toward master (e.g. 3.7-dev, then 3.8-dev, then master), testing each branch locally and stopping before the push. Use only when the operator explicitly asks to merge a pull request, a feature branch, or commits already on a release branch.","apache\u002Ftinkerpop","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACG106047V1J755TAB62T9",2155,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-merge\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,9,43,44,45,46,47,48],"tinker merge","Tinker","merge","maven","cli","when","feature","branches","only","use","branch","work","gh","commits","testing","tinkerpop","push","pull","dev","git","release","pull request","2026-11-10 10:12:30",false,"---\nname: tinker-merge\ndescription: >\n  Merge work forward through Apache TinkerPop's release branches toward master\n  (e.g. 3.7-dev, then 3.8-dev, then master), testing each branch locally and\n  stopping before the push. Use only when the operator explicitly asks to\n  merge a pull request, a feature branch, or commits already on a release\n  branch.\nlicense: Apache-2.0\ncompatibility: Requires git and Maven, plus the gh CLI to merge a pull request. Each release branch needs the JDK its tinker-dev skill names.\nmetadata:\n  version: 1.1.0\n  project: Apache TinkerPop\n---\n\n# TinkerPop Merge Skill\n\nTinkerPop merges through its oldest release branch toward `master`: work that lands on `3.7-dev`\nis merged into `3.8-dev`, and `3.8-dev` into `master`. `scripts\u002Fmerge-forward.sh` performs that\nchain deterministically. Your part is the one question to the operator, the conflicts, and the\nhandoff. The branch rules behind it are in the Branches and Pull Requests sections of\n`docs\u002Fsrc\u002Fdev\u002Fdeveloper\u002Ffor-committers.asciidoc`.\n\n**Never push.** The run ends with local merges and a printed push command. The operator reviews\nthe result and pushes it. That rule in `AGENTS.md` has no exception here.\n\n## 1. Identify the source\n\nThe operator names what to merge. Pass it to the script as is:\n\n| The operator says | Source argument |\n|---|---|\n| a pull request number | `#1234` |\n| a feature branch | the branch name, e.g. `TINKERPOP-1234` |\n| \"merge 3.7-dev through\" after committing to it directly | the release branch, e.g. `3.7-dev` |\n\nThe script works out the chain itself: from the pull request's base branch, from the release\nbranch a feature branch was cut from, or from the named release branch. Pass `--onto \u003Cbranch>`\nonly when the operator states the target or the script says it cannot tell.\n\n## 2. Ask how to test — the only questions\n\nAsk the operator exactly this, with the default first:\n\n1. `mvn clean install` (default) → `--test default`\n2. `mvn clean install -DskipIntegrationTests=false` → `--test integration`\n3. Skip all testing → `--test skip`\n4. A command the operator gives → `--test-command '\u003Ccommand>'`\n\nUnless testing is skipped, also ask which branches in the chain to test, all of them by default.\nPass the ones the operator leaves out as `--skip-test-on \u003Cbranch>[,\u003Cbranch>]`: they are merged\nbut not tested, as when the operator trusts a build of the oldest branch to cover the rest.\n\nAsk nothing else before starting. Whichever command is chosen runs from the repository root on\nevery tested branch in the chain, after its merge, and a non-zero exit counts as a test failure.\nPass an operator's command through exactly as given, quoted as one argument.\nGLV modules are tested only where the clone has activated them (see the `tinker-dev` skill), so\nsay so if the operator chose testing and a GLV changed but its `.glv` sentinel is absent.\n\n## 3. Check the JDK for each branch\n\nRelease branches build on different JDKs. Each branch's own `tinker-dev` skill states which one\nin its `compatibility` line:\n\n```bash\ngit show \u003Cremote>\u002F\u003Cbranch>:.skills\u002Ftinker-dev\u002FSKILL.md | grep '^compatibility'\n```\n\nWhen the JDK on the path does not fit a branch in the chain, pin an installed one that does\nbefore starting, and tell the operator which you pinned:\n\n```bash\ngit config tinker-merge.\u003Cbranch>.javaHome \u003Cpath-to-jdk>\n```\n\nIf no suitable JDK is installed, stop and say so. Skip this step for branches that are not\ntested.\n\n## 4. Run it\n\n```bash\n.skills\u002Ftinker-merge\u002Fscripts\u002Fmerge-forward.sh \u003Csource> [--test \u003Cmode> | --test-command '\u003Ccmd>'] \\\n    [--skip-test-on \u003Cbranch>[,\u003Cbranch>]] [--onto \u003Cbranch>]\n```\n\nA tested run takes a long time, since each branch gets a full build. Run it in the background\nwith no short timeout. Before the first merge it prints the commits being merged. Read them: for\na pull request or a feature branch, every commit must belong to the work\n(`for-committers.asciidoc` makes that the committer's responsibility). Raise any that do not\nwith the operator and `--abort` unless they confirm.\n\nThe exit code says what happened:\n\n| Exit | Meaning | Do |\n|---|---|---|\n| `0` | Every branch merged and tested | Go to step 5 |\n| `1` | Refused before anything moved | Report the message. Do not work around it. |\n| `2` | Merge conflict, left in progress on that branch | Resolve per the conflict rules below, then `--continue` |\n| `3` | Tests failed on a branch; its log path is printed | Report the failure and stop |\n\n`--continue` resumes where the run stopped, and `--abort` returns every branch to where it was\nbefore the run, keeping any local commits the operator made before asking for the merge.\n\n### Conflicts\n\nCommit a resolution with git's default merge message (`git commit --no-edit`), then run\n`--continue`.\n\n- **Changelog and version files** (`CHANGELOG.asciidoc`, version numbers in `pom.xml` and the\n  GLV equivalents) are the expected conflicts. Keep both sides of a changelog conflict, with the\n  incoming entry under its own release's section. Keep the target branch's version numbers.\n- **Any other file:** resolve it, and in your report name each file and what you chose.\n- **If testing was skipped and the conflict is outside changelog and version files,** stop and\n  ask the operator before committing, since nothing would check the resolution.\n\n### Test failures\n\nA failure stops the run. Report the branch, the failing module and the relevant part of the log,\nthen wait. Fix nothing unless the operator asks. If they do, commit the fix on the branch that\nfailed first. Never weaken or skip a test to get through.\n\n`--continue` tests the failed branch again, as many times as the operator asks:\n\n- **Plain `--continue`** reruns the run's test command in full.\n- **`--continue --test-command '\u003Ccmd>'`** runs `\u003Ccmd>` instead, once, on that branch only. The\n  usual case is a Maven build resumed from the module that failed, such as\n  `mvn clean install -rf :gremlin-server`, since the modules before it already passed. The next\n  branch goes back to the run's test command. Use it only when the operator gives the command or\n  asks to resume.\n\n## 5. Hand off\n\nReport what each branch now holds beyond the remote, give the push command the script printed\n(`git push --atomic ...`, newest branch first), and stop. If the operator decides against the\nresult, run `--abort`.\n\nWhen the operator says the push has landed and the work has a root bead, continue with the\npin-at-merge step in `.beads\u002FPRIME.md` (section 4). The commit hashes are final at that point.\n","# TinkerPop Merge Skill\n\nTinkerPop merges through its oldest release branch toward `master`: work that lands on `3.7-dev`\nis merged into `3.8-dev`, and `3.8-dev` into `master`. `scripts\u002Fmerge-forward.sh` performs that\nchain deterministically. Your part is the one question to the operator, the conflicts, and the\nhandoff. The branch rules behind it are in the Branches and Pull Requests sections of\n`docs\u002Fsrc\u002Fdev\u002Fdeveloper\u002Ffor-committers.asciidoc`.\n\n**Never push.** The run ends with local merges and a printed push command. The operator reviews\nthe result and pushes it. That rule in `AGENTS.md` has no exception here.\n\n## 1. Identify the source\n\nThe operator names what to merge. Pass it to the script as is:\n\n| The operator says | Source argument |\n|---|---|\n| a pull request number | `#1234` |\n| a feature branch | the branch name, e.g. `TINKERPOP-1234` |\n| \"merge 3.7-dev through\" after committing to it directly | the release branch, e.g. `3.7-dev` |\n\nThe script works out the chain itself: from the pull request's base branch, from the release\nbranch a feature branch was cut from, or from the named release branch. Pass `--onto \u003Cbranch>`\nonly when the operator states the target or the script says it cannot tell.\n\n## 2. Ask how to test — the only questions\n\nAsk the operator exactly this, with the default first:\n\n1. `mvn clean install` (default) → `--test default`\n2. `mvn clean install -DskipIntegrationTests=false` → `--test integration`\n3. Skip all testing → `--test skip`\n4. A command the operator gives → `--test-command '\u003Ccommand>'`\n\nUnless testing is skipped, also ask which branches in the chain to test, all of them by default.\nPass the ones the operator leaves out as `--skip-test-on \u003Cbranch>[,\u003Cbranch>]`: they are merged\nbut not tested, as when the operator trusts a build of the oldest branch to cover the rest.\n\nAsk nothing else before starting. Whichever command is chosen runs from the repository root on\nevery tested branch in the chain, after its merge, and a non-zero exit counts as a test failure.\nPass an operator's command through exactly as given, quoted as one argument.\nGLV modules are tested only where the clone has activated them (see the `tinker-dev` skill), so\nsay so if the operator chose testing and a GLV changed but its `.glv` sentinel is absent.\n\n## 3. Check the JDK for each branch\n\nRelease branches build on different JDKs. Each branch's own `tinker-dev` skill states which one\nin its `compatibility` line:\n\n```bash\ngit show \u003Cremote>\u002F\u003Cbranch>:.skills\u002Ftinker-dev\u002FSKILL.md | grep '^compatibility'\n```\n\nWhen the JDK on the path does not fit a branch in the chain, pin an installed one that does\nbefore starting, and tell the operator which you pinned:\n\n```bash\ngit config tinker-merge.\u003Cbranch>.javaHome \u003Cpath-to-jdk>\n```\n\nIf no suitable JDK is installed, stop and say so. Skip this step for branches that are not\ntested.\n\n## 4. Run it\n\n```bash\n.skills\u002Ftinker-merge\u002Fscripts\u002Fmerge-forward.sh \u003Csource> [--test \u003Cmode> | --test-command '\u003Ccmd>'] \\\n    [--skip-test-on \u003Cbranch>[,\u003Cbranch>]] [--onto \u003Cbranch>]\n```\n\nA tested run takes a long time, since each branch gets a full build. Run it in the background\nwith no short timeout. Before the first merge it prints the commits being merged. Read them: for\na pull request or a feature branch, every commit must belong to the work\n(`for-committers.asciidoc` makes that the committer's responsibility). Raise any that do not\nwith the operator and `--abort` unless they confirm.\n\nThe exit code says what happened:\n\n| Exit | Meaning | Do |\n|---|---|---|\n| `0` | Every branch merged and tested | Go to step 5 |\n| `1` | Refused before anything moved | Report the message. Do not work around it. |\n| `2` | Merge conflict, left in progress on that branch | Resolve per the conflict rules below, then `--continue` |\n| `3` | Tests failed on a branch; its log path is printed | Report the failure and stop |\n\n`--continue` resumes where the run stopped, and `--abort` returns every branch to where it was\nbefore the run, keeping any local commits the operator made before asking for the merge.\n\n### Conflicts\n\nCommit a resolution with git's default merge message (`git commit --no-edit`), then run\n`--continue`.\n\n- **Changelog and version files** (`CHANGELOG.asciidoc`, version numbers in `pom.xml` and the\n  GLV equivalents) are the expected conflicts. Keep both sides of a changelog conflict, with the\n  incoming entry under its own release's section. Keep the target branch's version numbers.\n- **Any other file:** resolve it, and in your report name each file and what you chose.\n- **If testing was skipped and the conflict is outside changelog and version files,** stop and\n  ask the operator before committing, since nothing would check the resolution.\n\n### Test failures\n\nA failure stops the run. Report the branch, the failing module and the relevant part of the log,\nthen wait. Fix nothing unless the operator asks. If they do, commit the fix on the branch that\nfailed first. Never weaken or skip a test to get through.\n\n`--continue` tests the failed branch again, as many times as the operator asks:\n\n- **Plain `--continue`** reruns the run's test command in full.\n- **`--continue --test-command '\u003Ccmd>'`** runs `\u003Ccmd>` instead, once, on that branch only. The\n  usual case is a Maven build resumed from the module that failed, such as\n  `mvn clean install -rf :gremlin-server`, since the modules before it already passed. The next\n  branch goes back to the run's test command. Use it only when the operator gives the command or\n  asks to resume.\n\n## 5. Hand off\n\nReport what each branch now holds beyond the remote, give the push command the script printed\n(`git push --atomic ...`, newest branch first), and stop. If the operator decides against the\nresult, run `--abort`.\n\nWhen the operator says the push has landed and the work has a root bead, continue with the\npin-at-merge step in `.beads\u002FPRIME.md` (section 4). The commit hashes are final at that point.\n",{"name":5,"license":15,"metadata":54,"description":57,"compatibility":58},{"project":55,"version":56},"Apache TinkerPop","1.1.0","Merge work forward through Apache TinkerPop's release branches toward master (e.g. 3.7-dev, then 3.8-dev, then master), testing each branch locally and stopping before the push. Use only when the operator explicitly asks to merge a pull request, a feature branch, or commits already on a release branch.\n","Requires git and Maven, plus the gh CLI to merge a pull request. Each release branch needs the JDK its tinker-dev skill names.","master","6909f4b34ff2a7f485ad67355b72ca41804513db",".skills\u002Ftinker-merge",864,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop","https:\u002F\u002Ftinkerpop.apache.org\u002F","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-14 08:48:41",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add apache\u002Ftinkerpop --skill tinker-merge",{"tool":74,"command":75},"bunx","bunx skills add apache\u002Ftinkerpop --skill tinker-merge",{"tool":77,"command":78},"pnpm","pnpm dlx skills add apache\u002Ftinkerpop --skill tinker-merge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-merge\u002FSKILL.md",true,[82,88,92],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"DESIGN.md","REFERENCE","参考文档",2544,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-merge\u002FDESIGN.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"ONBOARDING.md",6167,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-sdk-for-net\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fprovisioning-library-generation\u002FONBOARDING.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fmerge-forward.sh","SCRIPT","脚本",16573,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-merge\u002Fscripts\u002Fmerge-forward.sh",[99,130,163],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":109,"publishedAt":49},"01M6ACGDJBHVT4P5M3EV93MQAR","tinker-review","Graph-based PR review for Apache TinkerPop. Builds a knowledge graph from PR source code, enriches it with semantic relationships guided by domain playbooks, runs structural analysis, and produces an HTML evidence package. Use when asked to review a TinkerPop PR by number.","https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-review\u002FSKILL.md",[105,106],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[28,110,111,112,46,113,114,115,9,42,116,117,118,119,120,32,121,122,123,124,125,126,127,128,129],"review","tinker review","package","docker","pr review","pr","code","graph","structural","knowledge","access","number","analysis","beads","knowledge graph","node","network","source","source code","html",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":144,"publishedAt":49},"01M6ACG7R07AC5ABZ472F0B3MF","tinker-doc","Writing, editing and reviewing documentation for the Apache TinkerPop project. Use  when  authoring or revising any content under docs\u002Fsrc\u002F — reference docs, recipes, tutorials, upgrade\u002Frelease notes, provider and developer guides — or the CHANGELOG. Covers the TinkerPop documentation voice and the per-book style expectations, the executable Gremlin code-block pipeline, and AsciiDoc conventions. For building and validating code changes, see tinker-dev.","https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-doc\u002FSKILL.md",[136,141],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":142,"categoryName":143,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000036","内容创作者",[28,145,146,147,148,149,150,32,151,152,153,154,155,42,156,9,47,45,157,158,159,116,160,161,162],"doc","tinker doc","authoring","src","markdown","guides","upgrade","pipeline","documentation","gremlin","notes","changelog","release notes","writing","docs","content","never","project",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":173,"publishedAt":49},"01M6ACG48DAG4N1P036ZP8V8P5","tinker-dev","Development guidance for the Apache TinkerPop monorepo. Use when building, testing, or contributing to TinkerPop's graph computing framework and its multi-language Gremlin ecosystem (Java, Python, JavaScript, .NET, Go). Covers coding conventions, build recipes, test evaluation, documentation, development environment setup, and Gremlin MCP server usage.","https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-dev\u002FSKILL.md",[169,170],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[45,28,174,41,175,176,177,178,179,180,125,181,182,183,117,184,185,32,9,186,153,187],"tinker dev","MCP","framework","ecosystem","monorepo","coding conventions","server","Evaluation","recipes","coding","development environment","contributing","go","mcp server"]