[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACG48DAG4N1P036ZP8V8P5":3,"skill-same:01M6ACG48DAG4N1P036ZP8V8P5":101},{"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":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":6,"updatedAt":66,"install":67,"resources":80},"01M6ACG48DAG4N1P036ZP8V8P5","tinker-dev",null,"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.","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-dev\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,9,44,45,46,47],"dev","tinker dev","Tinker","when","development environment","graph","coding","recipes","Evaluation","node","server","coding conventions","monorepo","ecosystem","framework","go","contributing","documentation","mcp server","MCP","testing","2026-11-10 10:12:30",false,"---\nname: tinker-dev\ndescription: >\n  Development guidance for the Apache TinkerPop monorepo. Use when building,\n  testing, or contributing to TinkerPop's graph computing framework and its\n  multi-language Gremlin ecosystem (Java, Python, JavaScript, .NET, Go).\n  Covers coding conventions, build recipes, test evaluation, documentation,\n  development environment setup, and Gremlin MCP server usage.\nlicense: Apache-2.0\ncompatibility: Requires Java 17, 21, or 25, Maven 3.6.3+, Docker. Individual GLVs may need Python, Node.js, .NET SDK, or Go.\nmetadata:\n  version: 1.0.0\n  project: Apache TinkerPop\n---\n\n# TinkerPop Development Skill\n\n## Project Overview\n\nApache TinkerPop is a graph computing framework providing a standard API (the Gremlin graph\ntraversal language) for graph databases and processors. The repository is a Maven multi-module\nmonorepo that wraps JVM code, Python, JavaScript\u002FTypeScript, .NET, and Go under a single build.\n\nCanonical project documentation (prefer local files over external URLs):\n\n- `README.md` and `CONTRIBUTING.md` at the repo root\n- Reference docs: `docs\u002Fsrc\u002Freference\u002F`\n- Developer docs: `docs\u002Fsrc\u002Fdev\u002Fdeveloper\u002F`\n- Provider docs and Gremlin Semantics: `docs\u002Fsrc\u002Fdev\u002Fprovider\u002F`\n- IO and Serialization: `docs\u002Fsrc\u002Fdev\u002Fio\u002F`\n- Recipes: `docs\u002Fsrc\u002Frecipes\u002F`\n- Upgrade docs: `docs\u002Fsrc\u002Fupgrade\u002F`\n- Future plans: `docs\u002Fsrc\u002Fdev\u002Ffuture\u002F`\n\n## Definition of Done\n\nA change is **not done** until a full Maven validation has passed locally. Run it before\npresenting work for review — even when your targeted or unit tests already pass, and even if you\njudge a full run unnecessary. Incremental testing during development is encouraged, but it does\n**not** satisfy this gate.\n\nValidation is two steps. First, rebuild and install the whole reactor so every module picks up\nyour changes:\n\n```bash\nmvn clean install -DskipTests\n```\n\nThen run `verify` scoped to what you changed, using the **broadest** rule that applies, and\nalways list every module you touched.\n\n**Self-contained modules** — changing one of these only requires validating that module:\n\n| Changed module | Validate command |\n|---|---|\n| Python GLV | `mvn verify -pl gremlin-python` |\n| JavaScript GLV | `mvn verify -pl :gremlin-javascript` |\n| .NET GLV | `mvn verify -pl :gremlin-dotnet,:gremlin-dotnet-source,:gremlin-dotnet-tests` |\n| Go GLV | `mvn verify -pl :gremlin-go` |\n| `gremlint` | `mvn verify -pl :gremlint` |\n| `gremlin-mcp` | `mvn verify -pl :gremlin-mcp` |\n| Other single JVM module (e.g. `tinkergraph-gremlin`, `gremlin-console`) | `mvn verify -pl \u003Cmodule> -DskipIntegrationTests=false` |\n\n**Shared modules** — depended on by others, so changing them means validating the consumers too.\nUse the broadest rule that matches:\n\n- **`gremlin-server`, `gremlin-driver`, or `gremlin-util`** define the wire protocol and\n  serialization that every GLV exercises → validate the changed module(s) **plus all GLVs**:\n  `mvn verify -pl \u003Cchanged>,gremlin-python,:gremlin-javascript,:gremlin-dotnet,:gremlin-dotnet-source,:gremlin-dotnet-tests,:gremlin-go -DskipIntegrationTests=false`\n- **`gremlin-core`, `gremlin-test`, or anything they depend on** ripple across the whole project,\n  including the OLAP engines (`hadoop-gremlin`, `spark-gremlin`) → run everything:\n  `mvn clean install -DskipIntegrationTests=false`\n- **Unsure?** Treat it as the `gremlin-core` case and run everything.\n\n**Docs or code comments only** — no validation gate; this gate is for changes that affect behavior.\n\n### Things that quietly invalidate a run\n\n- **GLV tests are skipped unless activated.** A GLV is built and tested only when its `.glv`\n  sentinel exists: `gremlin-python\u002F.glv`, `gremlin-go\u002F.glv`, and *both* `gremlin-dotnet\u002Fsrc\u002F.glv`\n  and `gremlin-dotnet\u002Ftest\u002F.glv` (JavaScript builds by default). Without the sentinel the module\n  is silently skipped — a green run may have tested nothing of your change. Create the sentinel\n  (or pass `-Pglv-python` \u002F `-Pglv-go`) before validating a GLV change.\n- **Grammar and feature-test changes need a reactor build to take effect.** The ANTLR grammar\n  (`gremlin-language\u002Fsrc\u002Fmain\u002Fantlr4\u002FGremlin.g4`) and the Gherkin features under `gremlin-test`\n  drive code generation during `mvn clean install` — ANTLR parsers, and per-language test code\n  generated from the feature corpus (e.g. `gremlin-python\u002Fbuild\u002Fgenerate.groovy`, with\n  equivalents for Go, .NET, and JavaScript). After changing either, run `mvn clean install\n  -DskipTests` before relying on *any* test, including fast native ones, or you will be testing\n  stale generated code.\n- **Judge pass\u002Ffail by the Maven exit code, not console text.** Do not `grep`\u002F`tail` the build\n  output — tests deliberately emit expected errors, so the log misleads. Exit `0` = pass. For\n  Python, detailed per-suite results are in `gremlin-python\u002Ftarget\u002Fpython3\u002Fpython-reports\u002F*.xml`.\n\nIf you cannot run the validation (for example, Docker is unavailable), say so explicitly and\nreport the change as **not validated** — do not present it as done.\n\n## Repository Structure\n\nMost module names map directly to their purpose (`gremlin-core`, `gremlin-server`,\n`gremlin-go`, etc.). Two things that aren't obvious:\n\n- The **JavaScript workspace lives under `gremlin-js\u002F`** — it contains `gremlin-javascript\u002F`\n  (the `gremlin` npm driver), `gremlin-mcp\u002F`, and `gremlint\u002F`. There is no top-level\n  `gremlin-javascript\u002F` directory.\n- **Maven orchestrates the build for every module, including the non-JVM ones** (Python,\n  JavaScript, .NET, Go) — which is why the validation in the Definition of Done runs through\n  Maven rather than each language's native test runner.\n\nCross-language Gherkin feature tests live in `gremlin-test\u002F`.\n\n## Basic Build Commands\n\nBuild everything:\n```bash\nmvn clean install\n```\n\nBuild a specific module:\n```bash\nmvn clean install -pl \u003Cmodule-name>\n```\n\nFor GLV-specific builds and the validation commands per module, see the **Definition of Done**\ntable above. For environment setup and GLV activation, see `references\u002Fdev-environment-setup.md`.\n\n## Conventions\n\nThe general Do\u002FDon't rules and \"when in doubt\" guidance live in the root `AGENTS.md` — the\nsingle source of truth, not repeated here. The conventions below are the TinkerPop-specific\nones that are easy to miss:\n\n- **License header**: every new file needs the ASF header. Canonical text: `bin\u002Fasf-license-header.txt`.\n- **Test naming**: a test using a `GraphProvider` with `AbstractGremlinTest` is suffixed\n  `Check`, not `Test`.\n- **Gremlin language tests**: cross-language behavior is tested with Gherkin features under\n  `gremlin-test\u002Fsrc\u002Fmain\u002Fresources\u002Forg\u002Fapache\u002Ftinkerpop\u002Fgremlin\u002Ftest\u002Ffeatures\u002F`\n  (see `docs\u002Fsrc\u002Fdev\u002Fdeveloper\u002Ffor-committers.asciidoc`). When adding or changing an intent\n  (`And the intent`), follow the intent guidance there.\n- **Docs are AsciiDoc** under `docs\u002Fsrc\u002F` — never Markdown in the main docs tree. For writing or\n  revising any documentation (voice, per-book style, executable code blocks, AsciiDoc wiring),\n  use the **tinker-doc** skill. The mechanical minimum: add new content to the right book and update\n  its `index.asciidoc`.\n- **Changelog**: for user-visible or API changes, add a concise `CHANGELOG.asciidoc` entry in the\n  correct version section. Do not invent version numbers or release names. Never add the\n  `*(breaking)*` marker to an entry you write: it is applied only at release, to the lines generated\n  from JIRA issues labelled `breaking` (see `docs\u002Fsrc\u002Fdev\u002Fdeveloper\u002Frelease.asciidoc`), so a\n  hand-written entry without it is correct. Explain a breaking change in the upgrade docs instead.\n  See the **tinker-doc** skill for changelog discipline (one entry per user-facing change, not per\n  commit) and voice.\n\nOtherwise, match the existing code in neighboring files — explicit imports (no wildcards),\n`final` where practical, SLF4J logging over `println`, Hamcrest matchers, and closing any\n`Graph` you construct in a test.\n\n## Reference Guides\n\nBuild and validate commands live in the **Definition of Done** table above. For the remaining\ntask-specific guidance, see:\n\n- [Development Environment Setup](references\u002Fdev-environment-setup.md) — fresh clone to working environment, prerequisites, GLV activation\n- [Gremlin MCP Server](references\u002Fgremlin-mcp.md) — translation, formatting, querying via MCP\n","# TinkerPop Development Skill\n\n## Project Overview\n\nApache TinkerPop is a graph computing framework providing a standard API (the Gremlin graph\ntraversal language) for graph databases and processors. The repository is a Maven multi-module\nmonorepo that wraps JVM code, Python, JavaScript\u002FTypeScript, .NET, and Go under a single build.\n\nCanonical project documentation (prefer local files over external URLs):\n\n- `README.md` and `CONTRIBUTING.md` at the repo root\n- Reference docs: `docs\u002Fsrc\u002Freference\u002F`\n- Developer docs: `docs\u002Fsrc\u002Fdev\u002Fdeveloper\u002F`\n- Provider docs and Gremlin Semantics: `docs\u002Fsrc\u002Fdev\u002Fprovider\u002F`\n- IO and Serialization: `docs\u002Fsrc\u002Fdev\u002Fio\u002F`\n- Recipes: `docs\u002Fsrc\u002Frecipes\u002F`\n- Upgrade docs: `docs\u002Fsrc\u002Fupgrade\u002F`\n- Future plans: `docs\u002Fsrc\u002Fdev\u002Ffuture\u002F`\n\n## Definition of Done\n\nA change is **not done** until a full Maven validation has passed locally. Run it before\npresenting work for review — even when your targeted or unit tests already pass, and even if you\njudge a full run unnecessary. Incremental testing during development is encouraged, but it does\n**not** satisfy this gate.\n\nValidation is two steps. First, rebuild and install the whole reactor so every module picks up\nyour changes:\n\n```bash\nmvn clean install -DskipTests\n```\n\nThen run `verify` scoped to what you changed, using the **broadest** rule that applies, and\nalways list every module you touched.\n\n**Self-contained modules** — changing one of these only requires validating that module:\n\n| Changed module | Validate command |\n|---|---|\n| Python GLV | `mvn verify -pl gremlin-python` |\n| JavaScript GLV | `mvn verify -pl :gremlin-javascript` |\n| .NET GLV | `mvn verify -pl :gremlin-dotnet,:gremlin-dotnet-source,:gremlin-dotnet-tests` |\n| Go GLV | `mvn verify -pl :gremlin-go` |\n| `gremlint` | `mvn verify -pl :gremlint` |\n| `gremlin-mcp` | `mvn verify -pl :gremlin-mcp` |\n| Other single JVM module (e.g. `tinkergraph-gremlin`, `gremlin-console`) | `mvn verify -pl \u003Cmodule> -DskipIntegrationTests=false` |\n\n**Shared modules** — depended on by others, so changing them means validating the consumers too.\nUse the broadest rule that matches:\n\n- **`gremlin-server`, `gremlin-driver`, or `gremlin-util`** define the wire protocol and\n  serialization that every GLV exercises → validate the changed module(s) **plus all GLVs**:\n  `mvn verify -pl \u003Cchanged>,gremlin-python,:gremlin-javascript,:gremlin-dotnet,:gremlin-dotnet-source,:gremlin-dotnet-tests,:gremlin-go -DskipIntegrationTests=false`\n- **`gremlin-core`, `gremlin-test`, or anything they depend on** ripple across the whole project,\n  including the OLAP engines (`hadoop-gremlin`, `spark-gremlin`) → run everything:\n  `mvn clean install -DskipIntegrationTests=false`\n- **Unsure?** Treat it as the `gremlin-core` case and run everything.\n\n**Docs or code comments only** — no validation gate; this gate is for changes that affect behavior.\n\n### Things that quietly invalidate a run\n\n- **GLV tests are skipped unless activated.** A GLV is built and tested only when its `.glv`\n  sentinel exists: `gremlin-python\u002F.glv`, `gremlin-go\u002F.glv`, and *both* `gremlin-dotnet\u002Fsrc\u002F.glv`\n  and `gremlin-dotnet\u002Ftest\u002F.glv` (JavaScript builds by default). Without the sentinel the module\n  is silently skipped — a green run may have tested nothing of your change. Create the sentinel\n  (or pass `-Pglv-python` \u002F `-Pglv-go`) before validating a GLV change.\n- **Grammar and feature-test changes need a reactor build to take effect.** The ANTLR grammar\n  (`gremlin-language\u002Fsrc\u002Fmain\u002Fantlr4\u002FGremlin.g4`) and the Gherkin features under `gremlin-test`\n  drive code generation during `mvn clean install` — ANTLR parsers, and per-language test code\n  generated from the feature corpus (e.g. `gremlin-python\u002Fbuild\u002Fgenerate.groovy`, with\n  equivalents for Go, .NET, and JavaScript). After changing either, run `mvn clean install\n  -DskipTests` before relying on *any* test, including fast native ones, or you will be testing\n  stale generated code.\n- **Judge pass\u002Ffail by the Maven exit code, not console text.** Do not `grep`\u002F`tail` the build\n  output — tests deliberately emit expected errors, so the log misleads. Exit `0` = pass. For\n  Python, detailed per-suite results are in `gremlin-python\u002Ftarget\u002Fpython3\u002Fpython-reports\u002F*.xml`.\n\nIf you cannot run the validation (for example, Docker is unavailable), say so explicitly and\nreport the change as **not validated** — do not present it as done.\n\n## Repository Structure\n\nMost module names map directly to their purpose (`gremlin-core`, `gremlin-server`,\n`gremlin-go`, etc.). Two things that aren't obvious:\n\n- The **JavaScript workspace lives under `gremlin-js\u002F`** — it contains `gremlin-javascript\u002F`\n  (the `gremlin` npm driver), `gremlin-mcp\u002F`, and `gremlint\u002F`. There is no top-level\n  `gremlin-javascript\u002F` directory.\n- **Maven orchestrates the build for every module, including the non-JVM ones** (Python,\n  JavaScript, .NET, Go) — which is why the validation in the Definition of Done runs through\n  Maven rather than each language's native test runner.\n\nCross-language Gherkin feature tests live in `gremlin-test\u002F`.\n\n## Basic Build Commands\n\nBuild everything:\n```bash\nmvn clean install\n```\n\nBuild a specific module:\n```bash\nmvn clean install -pl \u003Cmodule-name>\n```\n\nFor GLV-specific builds and the validation commands per module, see the **Definition of Done**\ntable above. For environment setup and GLV activation, see `references\u002Fdev-environment-setup.md`.\n\n## Conventions\n\nThe general Do\u002FDon't rules and \"when in doubt\" guidance live in the root `AGENTS.md` — the\nsingle source of truth, not repeated here. The conventions below are the TinkerPop-specific\nones that are easy to miss:\n\n- **License header**: every new file needs the ASF header. Canonical text: `bin\u002Fasf-license-header.txt`.\n- **Test naming**: a test using a `GraphProvider` with `AbstractGremlinTest` is suffixed\n  `Check`, not `Test`.\n- **Gremlin language tests**: cross-language behavior is tested with Gherkin features under\n  `gremlin-test\u002Fsrc\u002Fmain\u002Fresources\u002Forg\u002Fapache\u002Ftinkerpop\u002Fgremlin\u002Ftest\u002Ffeatures\u002F`\n  (see `docs\u002Fsrc\u002Fdev\u002Fdeveloper\u002Ffor-committers.asciidoc`). When adding or changing an intent\n  (`And the intent`), follow the intent guidance there.\n- **Docs are AsciiDoc** under `docs\u002Fsrc\u002F` — never Markdown in the main docs tree. For writing or\n  revising any documentation (voice, per-book style, executable code blocks, AsciiDoc wiring),\n  use the **tinker-doc** skill. The mechanical minimum: add new content to the right book and update\n  its `index.asciidoc`.\n- **Changelog**: for user-visible or API changes, add a concise `CHANGELOG.asciidoc` entry in the\n  correct version section. Do not invent version numbers or release names. Never add the\n  `*(breaking)*` marker to an entry you write: it is applied only at release, to the lines generated\n  from JIRA issues labelled `breaking` (see `docs\u002Fsrc\u002Fdev\u002Fdeveloper\u002Frelease.asciidoc`), so a\n  hand-written entry without it is correct. Explain a breaking change in the upgrade docs instead.\n  See the **tinker-doc** skill for changelog discipline (one entry per user-facing change, not per\n  commit) and voice.\n\nOtherwise, match the existing code in neighboring files — explicit imports (no wildcards),\n`final` where practical, SLF4J logging over `println`, Hamcrest matchers, and closing any\n`Graph` you construct in a test.\n\n## Reference Guides\n\nBuild and validate commands live in the **Definition of Done** table above. For the remaining\ntask-specific guidance, see:\n\n- [Development Environment Setup](references\u002Fdev-environment-setup.md) — fresh clone to working environment, prerequisites, GLV activation\n- [Gremlin MCP Server](references\u002Fgremlin-mcp.md) — translation, formatting, querying via MCP\n",{"name":5,"license":15,"metadata":53,"description":56,"compatibility":57},{"project":54,"version":55},"Apache TinkerPop","1.0.0","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.\n","Requires Java 17, 21, or 25, Maven 3.6.3+, Docker. Individual GLVs may need Python, Node.js, .NET SDK, or Go.","master","da40b64fd486d889a8a363563e781272c764e8fa",".skills\u002Ftinker-dev",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":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add apache\u002Ftinkerpop --skill tinker-dev",{"tool":73,"command":74},"bunx","bunx skills add apache\u002Ftinkerpop --skill tinker-dev",{"tool":76,"command":77},"pnpm","pnpm dlx skills add apache\u002Ftinkerpop --skill tinker-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-dev\u002FSKILL.md",true,[81,87,91,95],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"DESIGN.md","REFERENCE","参考文档",1671,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-dev\u002FDESIGN.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fdev-environment-setup.md",3943,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-dev\u002Freferences\u002Fdev-environment-setup.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fgremlin-mcp.md",2916,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-dev\u002Freferences\u002Fgremlin-mcp.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fcheck-env.sh","SCRIPT","脚本",5077,"https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-dev\u002Fscripts\u002Fcheck-env.sh",[102,133,160],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":112,"publishedAt":48},"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",[108,109],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[29,113,114,115,116,117,9,118,119,120,121,122,123,36,124,125,126,127,30,128,129,130,32,131,132],"tinker review","review","pr review","git","pr","tinkerpop","number","html","source code","source","network","knowledge graph","beads","analysis","docker","access","knowledge","structural","code","package",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":143,"publishedAt":48},"01M6ACGAP25ER09HE3H2FJ9DJA","tinker-merge","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.","https:\u002F\u002Fgithub.com\u002Fapache\u002Ftinkerpop\u002Fblob\u002Fmaster\u002F.skills\u002Ftinker-merge\u002FSKILL.md",[139,142],{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[29,144,145,146,30,147,148,149,150,151,152,27,153,154,118,155,156,9,157,158,47,116,159],"merge","tinker merge","work","use","gh","only","branches","commits","feature","maven","pull","push","cli","pull request","release","branch",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":174,"publishedAt":48},"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",[166,171],{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":172,"categoryName":173,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000036","内容创作者",[175,29,176,27,177,178,179,180,131,181,182,183,184,158,9,185,118,186,44,187,30,188,189,190,191],"tinker doc","doc","pipeline","project","never","content","docs","writing","release notes","upgrade","changelog","notes","gremlin","guides","markdown","src","authoring"]