[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BXW84VW3MEZFCDB5HXTGPN":3,"skill-same:01M6BXW84VW3MEZFCDB5HXTGPN":59},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M6BXW84VW3MEZFCDB5HXTGPN","repo-init",null,"Initialize a repository with devenv, direnv, and jj (Jujutsu). Use when setting up a new project, initializing a repo, or when the user mentions devenv, direnv, or jj setup together.","vjrasane\u002Fdotfiles","vjrasane","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3148501?v=4","01M6BXVXZN07KKKXF9Q8JNN90K","Ville Räsänen","01M6BXVY3R8G19AN5BRA73H85R",0,"GPL-2.0","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Frepo-init\u002FSKILL.md",[],[19,20,21,22,23,24,25],"init","repo init","directory","setup","repository","new project","jj","2026-11-10 10:12:30",false,"---\nname: repo-init\ndescription: Initialize a repository with devenv, direnv, and jj (Jujutsu). Use when setting up a new project, initializing a repo, or when the user mentions devenv, direnv, or jj setup together.\nargument-hint: [project directory]\n---\n\n# Repo Init\n\nBootstrap a repository with the standard development tooling: devenv, direnv, and jj.\n\n## Instructions\n\n### Step 1: Determine the target directory\n\n- If the user provides a directory, use it\n- If a directory name is given but doesn't exist, create it\n- Otherwise use the current working directory\n- Confirm the directory is correct before proceeding\n\n### Step 2: Initialize jj (Jujutsu)\n\nInitialize a colocated jj repository. Colocated mode keeps a `.git` directory alongside `.jj` so that tools expecting git still work.\n\n```bash\ncd \u003Ctarget-dir>\njj git init --colocate\n```\n\nIf the directory already has a `.git` repo but no `.jj`:\n\n```bash\njj git init --colocate\n```\n\nIf `.jj` already exists, skip this step.\n\nAfter initializing, ask the user what the main\u002Ftrunk branch name is (usually `main`), then configure the trunk revset alias in `.jj\u002Frepo\u002Fconfig.toml`:\n\n```toml\n#:schema https:\u002F\u002Fdocs.jj-vcs.dev\u002Flatest\u002Fconfig-schema.json\n\n[revset-aliases]\n\"trunk()\" = \"main@origin\"\n```\n\nReplace `main` with the actual trunk branch name if different.\n\n### Step 3: Set up devenv\n\nCreate a `devenv.nix` file if one doesn't exist:\n\n```nix\n{\n  pkgs,\n  config,\n  ...\n}:\n{\n  packages = with pkgs; [\n    just\n  ];\n\n  claude.code.enable = true;\n\n  claude.code.mcpServers = {\n    devenv = {\n      type = \"stdio\";\n      command = \"devenv\";\n      args = [ \"mcp\" ];\n      env = {\n        DEVENV_ROOT = config.devenv.root;\n      };\n    };\n  };\n}\n```\n\n- `claude.code.enable = true` generates the project `.mcp.json` automatically\n- The `devenv` MCP server exposes `search_packages` and `search_options` tools so agents can search nixpkgs and devenv options when editing `devenv.nix`\n- `config` must be in the function arguments to reference `config.devenv.root`\n\nAlways include `just` — it is the standard task runner for all projects.\n\nAlso create a `justfile` in the project root if one doesn't exist:\n\n```just\ndefault:\n    @just --list\n```\n\nThis gives a useful default that lists all available recipes. The user will add project-specific recipes as needed.\n\nCreate a `devenv.yaml` file if one doesn't exist:\n\n```yaml\n# yaml-language-server: $schema=https:\u002F\u002Fdevenv.sh\u002Fdevenv.schema.json\ninputs:\n  nixpkgs:\n    url: github:cachix\u002Fdevenv-nixpkgs\u002Frolling\n```\n\nIf the user wants git-hooks via devenv, add the `git-hooks` input:\n\n```yaml\n  git-hooks:\n    url: github:cachix\u002Fgit-hooks.nix\n    inputs:\n      nixpkgs:\n        follows: nixpkgs\n```\n\n### Step 4: Set up direnv\n\nCreate a `.envrc` file if one doesn't exist:\n\n```bash\n# shellcheck shell=bash\nsource_up_if_exists\n\neval \"$(devenv direnvrc)\"\n\nuse devenv\n\nwatch_file .env\ndotenv_if_exists .env\n```\n\n- `source_up_if_exists` inherits parent `.envrc` files (useful for nested projects)\n- `watch_file .env` and `dotenv_if_exists .env` load environment variables from `.env` and reload when it changes\n\nThen allow it:\n\n```bash\ndirenv allow\n```\n\n### Step 5: Update .gitignore\n\nIf a `.gitignore` exists, merge these entries into it. If it doesn't exist, create one. Group entries under comments and preserve any existing content.\n\nThese entries MUST be present:\n\n```gitignore\n# Devenv\n.devenv*\ndevenv.local.nix\ndevenv.local.yaml\n\n# direnv\n.direnv\n\n# pre-commit\n.pre-commit-config.yaml\n\n# Environment\n.env\n\n# Claude\n.claude\u002F\n.mcp.json\n```\n\n- `.devenv*` covers `.devenv\u002F` (the devenv state directory) and `.devenv.flake.nix` (auto-generated flake)\n- `devenv.local.nix` and `devenv.local.yaml` are machine-specific overrides that shouldn't be committed\n- `.pre-commit-config.yaml` is auto-generated by devenv's git-hooks feature\n- `.claude\u002F` contains local agent state and settings that are per-user\n- `.mcp.json` is auto-generated by `claude.code.enable` in devenv\n\n### Step 6: Create AGENTS.md\n\nCreate a `AGENTS.md` file in the project root with agent instructions. If one already exists, merge these rules into it rather than overwriting.\n\nThe AGENTS.md MUST contain the following sections (adapt wording to fit existing content if merging):\n\n```markdown\n## Development Environment\n\nThis project uses **devenv** to manage development tools and dependencies. The environment activates automatically via direnv when you enter the project directory.\n\n- Install CLI tools and system-level dependencies via `devenv.nix` (under `packages`)\n- Do NOT use devenv for language-specific libraries — use the project's native package manager instead (npm, uv, pip, cargo, go modules, etc.)\n- To add a new tool: edit `devenv.nix`, then let direnv reload or run `devenv shell`\n\n## Version Control\n\nThis project uses **jj (Jujutsu)** for version control with git colocated mode. NEVER use git commands unless absolutely necessary (e.g., a tool has no jj support, or jj lacks the needed functionality). If you must use git, explain why.\n\njj quick reference:\n- `jj new` — start new work on top of current change\n- `jj describe -m \"message\"` — describe the current change\n- `jj commit -m \"message\"` — snapshot working copy and start a new change\n- `jj log` — view change history\n- `jj diff` — view uncommitted changes\n- `jj bookmark create \u003Cname>` — create a bookmark (branch equivalent)\n- `jj git fetch` — fetch from remote\n- `jj git push` — push to remote\n\nDo NOT use `git add`, `git commit`, `git push`, `git pull`, `git checkout`, `git switch`, `git branch`, or any other git porcelain command.\n\n## MCP Servers\n\nMCP servers for this project are managed through devenv. Add servers to `claude.code.mcpServers` in `devenv.nix` — devenv generates the `.mcp.json` file automatically. Use `\u002Fadd-mcp` to add common servers.\n```\n\n### Step 7: Create .claude\u002Fsettings.json (optional)\n\nIf the project doesn't have a `.claude\u002Fsettings.json`, ask the user if they want to create one. This can include project-specific permissions or MCP server settings.\n\n### Step 8: Verify the setup\n\nRun these checks:\n1. `jj status` works and shows the repo state\n2. `devenv shell -- echo \"devenv works\"` succeeds (or direnv has activated)\n3. `AGENTS.md` exists with the correct content\n4. `.envrc` exists and is allowed\n\nReport the results to the user.\n\n## Guidelines\n\n- Never overwrite existing files without asking — always check first and merge if needed\n- If jj is not installed, tell the user to add it to their global home.nix or install it\n- If devenv is not installed, tell the user to install it (it should be in their global home.nix)\n- If direnv is not installed, tell the user to add it to their global home.nix\n- Keep the generated devenv.nix minimal — don't add packages the user hasn't asked for\n- The AGENTS.md content is the most important part — it ensures all future agent sessions respect the tooling choices\n","# Repo Init\n\nBootstrap a repository with the standard development tooling: devenv, direnv, and jj.\n\n## Instructions\n\n### Step 1: Determine the target directory\n\n- If the user provides a directory, use it\n- If a directory name is given but doesn't exist, create it\n- Otherwise use the current working directory\n- Confirm the directory is correct before proceeding\n\n### Step 2: Initialize jj (Jujutsu)\n\nInitialize a colocated jj repository. Colocated mode keeps a `.git` directory alongside `.jj` so that tools expecting git still work.\n\n```bash\ncd \u003Ctarget-dir>\njj git init --colocate\n```\n\nIf the directory already has a `.git` repo but no `.jj`:\n\n```bash\njj git init --colocate\n```\n\nIf `.jj` already exists, skip this step.\n\nAfter initializing, ask the user what the main\u002Ftrunk branch name is (usually `main`), then configure the trunk revset alias in `.jj\u002Frepo\u002Fconfig.toml`:\n\n```toml\n#:schema https:\u002F\u002Fdocs.jj-vcs.dev\u002Flatest\u002Fconfig-schema.json\n\n[revset-aliases]\n\"trunk()\" = \"main@origin\"\n```\n\nReplace `main` with the actual trunk branch name if different.\n\n### Step 3: Set up devenv\n\nCreate a `devenv.nix` file if one doesn't exist:\n\n```nix\n{\n  pkgs,\n  config,\n  ...\n}:\n{\n  packages = with pkgs; [\n    just\n  ];\n\n  claude.code.enable = true;\n\n  claude.code.mcpServers = {\n    devenv = {\n      type = \"stdio\";\n      command = \"devenv\";\n      args = [ \"mcp\" ];\n      env = {\n        DEVENV_ROOT = config.devenv.root;\n      };\n    };\n  };\n}\n```\n\n- `claude.code.enable = true` generates the project `.mcp.json` automatically\n- The `devenv` MCP server exposes `search_packages` and `search_options` tools so agents can search nixpkgs and devenv options when editing `devenv.nix`\n- `config` must be in the function arguments to reference `config.devenv.root`\n\nAlways include `just` — it is the standard task runner for all projects.\n\nAlso create a `justfile` in the project root if one doesn't exist:\n\n```just\ndefault:\n    @just --list\n```\n\nThis gives a useful default that lists all available recipes. The user will add project-specific recipes as needed.\n\nCreate a `devenv.yaml` file if one doesn't exist:\n\n```yaml\n# yaml-language-server: $schema=https:\u002F\u002Fdevenv.sh\u002Fdevenv.schema.json\ninputs:\n  nixpkgs:\n    url: github:cachix\u002Fdevenv-nixpkgs\u002Frolling\n```\n\nIf the user wants git-hooks via devenv, add the `git-hooks` input:\n\n```yaml\n  git-hooks:\n    url: github:cachix\u002Fgit-hooks.nix\n    inputs:\n      nixpkgs:\n        follows: nixpkgs\n```\n\n### Step 4: Set up direnv\n\nCreate a `.envrc` file if one doesn't exist:\n\n```bash\n# shellcheck shell=bash\nsource_up_if_exists\n\neval \"$(devenv direnvrc)\"\n\nuse devenv\n\nwatch_file .env\ndotenv_if_exists .env\n```\n\n- `source_up_if_exists` inherits parent `.envrc` files (useful for nested projects)\n- `watch_file .env` and `dotenv_if_exists .env` load environment variables from `.env` and reload when it changes\n\nThen allow it:\n\n```bash\ndirenv allow\n```\n\n### Step 5: Update .gitignore\n\nIf a `.gitignore` exists, merge these entries into it. If it doesn't exist, create one. Group entries under comments and preserve any existing content.\n\nThese entries MUST be present:\n\n```gitignore\n# Devenv\n.devenv*\ndevenv.local.nix\ndevenv.local.yaml\n\n# direnv\n.direnv\n\n# pre-commit\n.pre-commit-config.yaml\n\n# Environment\n.env\n\n# Claude\n.claude\u002F\n.mcp.json\n```\n\n- `.devenv*` covers `.devenv\u002F` (the devenv state directory) and `.devenv.flake.nix` (auto-generated flake)\n- `devenv.local.nix` and `devenv.local.yaml` are machine-specific overrides that shouldn't be committed\n- `.pre-commit-config.yaml` is auto-generated by devenv's git-hooks feature\n- `.claude\u002F` contains local agent state and settings that are per-user\n- `.mcp.json` is auto-generated by `claude.code.enable` in devenv\n\n### Step 6: Create AGENTS.md\n\nCreate a `AGENTS.md` file in the project root with agent instructions. If one already exists, merge these rules into it rather than overwriting.\n\nThe AGENTS.md MUST contain the following sections (adapt wording to fit existing content if merging):\n\n```markdown\n## Development Environment\n\nThis project uses **devenv** to manage development tools and dependencies. The environment activates automatically via direnv when you enter the project directory.\n\n- Install CLI tools and system-level dependencies via `devenv.nix` (under `packages`)\n- Do NOT use devenv for language-specific libraries — use the project's native package manager instead (npm, uv, pip, cargo, go modules, etc.)\n- To add a new tool: edit `devenv.nix`, then let direnv reload or run `devenv shell`\n\n## Version Control\n\nThis project uses **jj (Jujutsu)** for version control with git colocated mode. NEVER use git commands unless absolutely necessary (e.g., a tool has no jj support, or jj lacks the needed functionality). If you must use git, explain why.\n\njj quick reference:\n- `jj new` — start new work on top of current change\n- `jj describe -m \"message\"` — describe the current change\n- `jj commit -m \"message\"` — snapshot working copy and start a new change\n- `jj log` — view change history\n- `jj diff` — view uncommitted changes\n- `jj bookmark create \u003Cname>` — create a bookmark (branch equivalent)\n- `jj git fetch` — fetch from remote\n- `jj git push` — push to remote\n\nDo NOT use `git add`, `git commit`, `git push`, `git pull`, `git checkout`, `git switch`, `git branch`, or any other git porcelain command.\n\n## MCP Servers\n\nMCP servers for this project are managed through devenv. Add servers to `claude.code.mcpServers` in `devenv.nix` — devenv generates the `.mcp.json` file automatically. Use `\u002Fadd-mcp` to add common servers.\n```\n\n### Step 7: Create .claude\u002Fsettings.json (optional)\n\nIf the project doesn't have a `.claude\u002Fsettings.json`, ask the user if they want to create one. This can include project-specific permissions or MCP server settings.\n\n### Step 8: Verify the setup\n\nRun these checks:\n1. `jj status` works and shows the repo state\n2. `devenv shell -- echo \"devenv works\"` succeeds (or direnv has activated)\n3. `AGENTS.md` exists with the correct content\n4. `.envrc` exists and is allowed\n\nReport the results to the user.\n\n## Guidelines\n\n- Never overwrite existing files without asking — always check first and merge if needed\n- If jj is not installed, tell the user to add it to their global home.nix or install it\n- If devenv is not installed, tell the user to install it (it should be in their global home.nix)\n- If direnv is not installed, tell the user to add it to their global home.nix\n- Keep the generated devenv.nix minimal — don't add packages the user hasn't asked for\n- The AGENTS.md content is the most important part — it ensures all future agent sessions respect the tooling choices\n",{"name":5,"description":7,"argument-hint":31},[32],"project directory","main","56fc291d843c7fcb046d00e4f557d565516019bb","llms\u002Fclaude\u002Fskills\u002Frepo-init","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fvjrasane","2026-11-05 23:04:06",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add vjrasane\u002Fdotfiles --skill repo-init",{"tool":45,"command":46},"bunx","bunx skills add vjrasane\u002Fdotfiles --skill repo-init",{"tool":48,"command":49},"pnpm","pnpm dlx skills add vjrasane\u002Fdotfiles --skill repo-init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Frepo-init\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"learnings-template.md","REFERENCE","参考文档",833,"https:\u002F\u002Fgithub.com\u002Fdandaka\u002Fskills\u002Fblob\u002Fmain\u002Fretrospective\u002Flearnings-template.md",[60,91,117,123,135,146],{"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":71,"publishedAt":26},"01M6PMCNSAK1GC3P7C5J49R3RE","start-ticket","Kick off work on a Linear ticket end to end — file or look up the ticket, create an isolated jj workspace for it, move into that workspace, pull the ticket, and brief its scope. Use when the user wants to start working on a subject or an existing ticket, \"start a ticket\", \"kick off LIN-123\", or spin up a workspace from a ticket and begin.","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Fstart-ticket\u002FSKILL.md",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[72,73,74,75,76,77,78,79,80,81,25,82,83,84,85,86,87,88,89,90],"start ticket","ticket","start","use","MCP","pull","file","brief","Bash","work on","linear ticket","up","end","scope","move","quick","URL","for","Existing",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":108,"publishedAt":26},"01M6BXWMYDB847PE9T0JR5J26K","writing-assistant","Help improve and flesh out written text in markdown or plain text files. Use when the user wants writing feedback, style fixes, grammar corrections, or help expanding bullet points into prose. Does not write text from scratch.","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Fwriting-assistant\u002FSKILL.md",[97,100,103],{"categoryNo":98,"categoryName":99,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":101,"categoryName":102,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[109,110,111,112,113,114,78,115,116],"assistant","writing assistant","writing","feedback","text","help","markdown","improve",{"skillNo":118,"name":119,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":26},"01M6BXWKJ4182T739T99VZFMHT","workspace","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Fworkspace\u002FSKILL.md",[],[119],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":26},"01M6BXWGV66SSKYFMCHTRKEDKK","skill-writer","Guide users through creating Agent Skills for Claude Code. Use when the user wants to create, write, author, or design a new Skill, or needs help with SKILL.md files, frontmatter, or skill structure.","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Fskill-writer\u002FSKILL.md",[129],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},[131,132,133,134,114],"skill writer","create","design","code",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":26},"01M6BXWF4JR4RRHJRSMRVS7BKQ","review","Review code changes for quality, security, and best practices","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Freview\u002FSKILL.md",[],[137,142,134,143,144,145],"security","best practices","review code","quality",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":156,"publishedAt":26},"01M6BXWCGMN7YPSZ71AG207YSW","review-mr","Find the GitLab merge request for the current jj branch and run a code review on it. Use when the user wants to review the MR, review the merge request, review \"my MR\", or review the current branch's changes on GitLab.","https:\u002F\u002Fgithub.com\u002Fvjrasane\u002Fdotfiles\u002Fblob\u002Fmain\u002Fllms\u002Fclaude\u002Fskills\u002Freview-mr\u002FSKILL.md",[152,155],{"categoryNo":153,"categoryName":154,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},[157,137,158,159,76,80,25,134,160,161,132,162,163,164],"review mr","merge","diffs","run","linear","gitlab","plugin","code review"]