[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MDZ2DRB45G9V3BTJ6VXTK":3,"skill-same:01M77MDZ2DRB45G9V3BTJ6VXTK":62},{"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":6,"updatedAt":29,"install":30,"resources":43},"01M77MDZ2DRB45G9V3BTJ6VXTK","developer-environment",null,"Use when installing or upgrading any tool, runtime, CLI, or library — brew, apt, npm i -g, pip install, cargo install, nvm, pyenv, asdf — editing mise.toml or .tool-versions, bumping or pinning versions, adding a dependency, hitting \"command not found\", setting up a dev or CI toolchain, reviewing Renovate or Dependabot version bumps, or considering Bazel.","rahulmutt\u002Fdevkit","rahulmutt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8035100?v=4","01M77MDP08WTFYCS2MD2Q580EJ","Rahul Muttineni","01M77MDP11EQ3MN8WV69GM6JKP",0,"MIT","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fdeveloper-environment\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: developer-environment\ndescription: Use when installing or upgrading any tool, runtime, CLI, or library — brew, apt, npm i -g, pip install, cargo install, nvm, pyenv, asdf — editing mise.toml or .tool-versions, bumping or pinning versions, adding a dependency, hitting \"command not found\", setting up a dev or CI toolchain, reviewing Renovate or Dependabot version bumps, or considering Bazel.\n---\n\n# Developer Environment\n\nInstall developer tools with **mise**, pinned to exact versions. Fall back to\n**devenv.nix** only when mise cannot provide the tool.\n\n1. **mise is the default** for languages, CLIs, and runtimes. One declarative\n   `mise.toml`, fast, per-project.\n2. **devenv.nix is the fallback** — only for what mise cannot supply (system\n   libraries, niche packages, anything needing the Nix ecosystem).\n\n## Always pin\n\nThe default command is:\n\n```bash\nmise use --pin \u003Ctool>@\u003Cversion>\n```\n\n`--pin` writes the fully-resolved exact version into `mise.toml` (e.g.\n`node = \"22.11.0\"`, not a fuzzy `node = \"22\"`), so checkouts are deterministic\nacross machines and CI. **Never use bare `mise use`** — an unpinned entry is a\nreproducibility bug.\n\n## Decision flow\n\n1. **Is the tool in the mise registry?** (`mise registry | grep \u003Ctool>`) →\n   `mise use --pin \u003Ctool>@\u003Cversion>`, commit `mise.toml`.\n2. **Not in the registry, but available on a mise backend** (asdf, aqua, ubi,\n   cargo, npm, pipx, go)? → install via that backend, still pinned, e.g.\n   `mise use --pin \"cargo:ripgrep@14.1.1\"`.\n3. **Genuinely unavailable through mise** (system lib, complex Nix derivation)?\n   → add it to `devenv.nix` (see\n   [`references\u002Fdevenv.nix`](references\u002Fdevenv.nix)).\n\nSee [`references\u002Fdecision-tree.md`](references\u002Fdecision-tree.md) for worked\nexamples.\n\n## Verify after installing\n\nNever claim a tool is installed without checking. After install:\n\n```bash\nmise install\n\u003Ctool> --version   # confirm the pinned version (use the binary's real name, e.g. rg for ripgrep)\n```\n\nIf the version printed does not match the pin, the install is not done.\n\n## Upgrading pinned versions\n\nA bump is a change like any other — it lands only when the project's full check\npasses.\n\n1. **See what's behind:** `mise outdated`, then `mise upgrade --bump` to rewrite\n   the pins in `mise.toml` (it keeps exact pins exact;\n   `mise upgrade\n\u003Ctool>@latest --bump` would write a floating `latest` —\n   don't).\n2. **Find every other pin of the same tools.** Versions also hide in CI\n   (`uses: owner\u002Faction@vN`, `setup-*` inputs), `.devcontainer\u002F`, Dockerfiles,\n   `package.json` `engines`, and `.tool-versions`. Update them together or the\n   environments diverge.\n3. **Run the full gate** (the repo's CI\u002Frelease task), not just `--version`.\n4. **On failure, check the old pin first** (`mise x \u003Ctool>@\u003Cold> -- \u003Ccmd>`). A\n   failure that reproduces on the old version predates the bump — fix it\n   separately and say so; don't blame or revert the bump for it.\n\n## Coexistence\n\nmise and devenv.nix can live in one repo: mise for the common case, devenv.nix\nfor the exceptions. Keep each tool in exactly one place — don't pin the same\ntool in both.\n\n## Application dependencies\n\nmise and devenv.nix provision the **toolchain**; a project's **application and\nlibrary dependencies** are owned by the language's native package manager —\n`npm`\u002F`pnpm`, `cargo`, `go mod`, `uv`\u002F`pip`, `cabal`. mise installs the package\nmanager (pinned); the package manager resolves the libraries.\n\n1. **Commit the lockfile.** A committed lockfile is the application-dependency\n   echo of pinning — it makes resolution deterministic across machines and CI.\n   Pin to exact versions, or to the tightest range your lockfile fully resolves;\n   never depend on a floating latest.\n2. **Every dependency is a liability.** Each one is code you don't control but\n   must read, update, and trust — `writing-clean-code`'s \"every line is a\n   liability\" carried into the supply chain. Prefer the standard library or one\n   small, well-maintained dependency over several overlapping ones, and weigh\n   the transitive cost before adding.\n3. **Update on a cadence, not in a panic.** Keep dependencies current with an\n   automated updater (Renovate, Dependabot) gated by CI, so upgrades land in\n   small reviewable steps instead of a risky big-bang bump.\n\nScanning those dependencies for known CVEs is `security-practices`' supply-chain\ncontrol (SCA), not this skill's job.\n\n## Build orchestration\n\nTool installation is one half of the environment; how the project _builds and\ntests_ is the other. **Default to each language's native build tooling** —\n`cargo`, `go build`, `npm`\u002F`pnpm`, `deno task`, Gradle. A meta-build system is a\ndeliberate, high-cost choice; don't adopt one without a trigger.\n\n### When to reach for Bazel\n\nAdopt Bazel only when one or more of these hold:\n\n1. **Polyglot monorepo** — multiple languages built and tested together, where\n   native per-language tools don't compose across the boundaries.\n2. **Build scale \u002F incrementality** — the codebase is large enough that a\n   fine-grained build graph materially cuts CI and local rebuild times.\n3. **Remote cache \u002F execution** — you need shared remote caching and\u002For remote\n   execution across a team or CI fleet.\n4. **Hermeticity & reproducibility** — strictly sandboxed, fully reproducible\n   builds are a hard requirement (the build-time echo of pinning).\n\nA single weak trigger rarely justifies the ongoing cost — `BUILD`-file upkeep\nand ruleset maintenance are permanent. Weigh it before committing.\n\nInstall Bazel the same mise-first way as any tool: pin `bazelisk` (the\nversion-managing launcher) and let `.bazelversion` pin Bazel itself.\n\n```bash\nmise use --pin bazelisk@\u003Cversion>   # then: echo \"\u003Cbazel-version>\" > .bazelversion\n```\n\nWhen a trigger holds and you're migrating, follow the phased path in\n[`references\u002Fbazel-migration.md`](references\u002Fbazel-migration.md).\n\n## Templates\n\nCopy and adapt:\n\n- [`references\u002Fmise.toml`](references\u002Fmise.toml) — pinned `[tools]`, `[env]`,\n  `[tasks]`.\n- [`references\u002Fdevenv.nix`](references\u002Fdevenv.nix) — minimal fallback shell.\n","# Developer Environment\n\nInstall developer tools with **mise**, pinned to exact versions. Fall back to\n**devenv.nix** only when mise cannot provide the tool.\n\n1. **mise is the default** for languages, CLIs, and runtimes. One declarative\n   `mise.toml`, fast, per-project.\n2. **devenv.nix is the fallback** — only for what mise cannot supply (system\n   libraries, niche packages, anything needing the Nix ecosystem).\n\n## Always pin\n\nThe default command is:\n\n```bash\nmise use --pin \u003Ctool>@\u003Cversion>\n```\n\n`--pin` writes the fully-resolved exact version into `mise.toml` (e.g.\n`node = \"22.11.0\"`, not a fuzzy `node = \"22\"`), so checkouts are deterministic\nacross machines and CI. **Never use bare `mise use`** — an unpinned entry is a\nreproducibility bug.\n\n## Decision flow\n\n1. **Is the tool in the mise registry?** (`mise registry | grep \u003Ctool>`) →\n   `mise use --pin \u003Ctool>@\u003Cversion>`, commit `mise.toml`.\n2. **Not in the registry, but available on a mise backend** (asdf, aqua, ubi,\n   cargo, npm, pipx, go)? → install via that backend, still pinned, e.g.\n   `mise use --pin \"cargo:ripgrep@14.1.1\"`.\n3. **Genuinely unavailable through mise** (system lib, complex Nix derivation)?\n   → add it to `devenv.nix` (see\n   [`references\u002Fdevenv.nix`](references\u002Fdevenv.nix)).\n\nSee [`references\u002Fdecision-tree.md`](references\u002Fdecision-tree.md) for worked\nexamples.\n\n## Verify after installing\n\nNever claim a tool is installed without checking. After install:\n\n```bash\nmise install\n\u003Ctool> --version   # confirm the pinned version (use the binary's real name, e.g. rg for ripgrep)\n```\n\nIf the version printed does not match the pin, the install is not done.\n\n## Upgrading pinned versions\n\nA bump is a change like any other — it lands only when the project's full check\npasses.\n\n1. **See what's behind:** `mise outdated`, then `mise upgrade --bump` to rewrite\n   the pins in `mise.toml` (it keeps exact pins exact;\n   `mise upgrade\n\u003Ctool>@latest --bump` would write a floating `latest` —\n   don't).\n2. **Find every other pin of the same tools.** Versions also hide in CI\n   (`uses: owner\u002Faction@vN`, `setup-*` inputs), `.devcontainer\u002F`, Dockerfiles,\n   `package.json` `engines`, and `.tool-versions`. Update them together or the\n   environments diverge.\n3. **Run the full gate** (the repo's CI\u002Frelease task), not just `--version`.\n4. **On failure, check the old pin first** (`mise x \u003Ctool>@\u003Cold> -- \u003Ccmd>`). A\n   failure that reproduces on the old version predates the bump — fix it\n   separately and say so; don't blame or revert the bump for it.\n\n## Coexistence\n\nmise and devenv.nix can live in one repo: mise for the common case, devenv.nix\nfor the exceptions. Keep each tool in exactly one place — don't pin the same\ntool in both.\n\n## Application dependencies\n\nmise and devenv.nix provision the **toolchain**; a project's **application and\nlibrary dependencies** are owned by the language's native package manager —\n`npm`\u002F`pnpm`, `cargo`, `go mod`, `uv`\u002F`pip`, `cabal`. mise installs the package\nmanager (pinned); the package manager resolves the libraries.\n\n1. **Commit the lockfile.** A committed lockfile is the application-dependency\n   echo of pinning — it makes resolution deterministic across machines and CI.\n   Pin to exact versions, or to the tightest range your lockfile fully resolves;\n   never depend on a floating latest.\n2. **Every dependency is a liability.** Each one is code you don't control but\n   must read, update, and trust — `writing-clean-code`'s \"every line is a\n   liability\" carried into the supply chain. Prefer the standard library or one\n   small, well-maintained dependency over several overlapping ones, and weigh\n   the transitive cost before adding.\n3. **Update on a cadence, not in a panic.** Keep dependencies current with an\n   automated updater (Renovate, Dependabot) gated by CI, so upgrades land in\n   small reviewable steps instead of a risky big-bang bump.\n\nScanning those dependencies for known CVEs is `security-practices`' supply-chain\ncontrol (SCA), not this skill's job.\n\n## Build orchestration\n\nTool installation is one half of the environment; how the project _builds and\ntests_ is the other. **Default to each language's native build tooling** —\n`cargo`, `go build`, `npm`\u002F`pnpm`, `deno task`, Gradle. A meta-build system is a\ndeliberate, high-cost choice; don't adopt one without a trigger.\n\n### When to reach for Bazel\n\nAdopt Bazel only when one or more of these hold:\n\n1. **Polyglot monorepo** — multiple languages built and tested together, where\n   native per-language tools don't compose across the boundaries.\n2. **Build scale \u002F incrementality** — the codebase is large enough that a\n   fine-grained build graph materially cuts CI and local rebuild times.\n3. **Remote cache \u002F execution** — you need shared remote caching and\u002For remote\n   execution across a team or CI fleet.\n4. **Hermeticity & reproducibility** — strictly sandboxed, fully reproducible\n   builds are a hard requirement (the build-time echo of pinning).\n\nA single weak trigger rarely justifies the ongoing cost — `BUILD`-file upkeep\nand ruleset maintenance are permanent. Weigh it before committing.\n\nInstall Bazel the same mise-first way as any tool: pin `bazelisk` (the\nversion-managing launcher) and let `.bazelversion` pin Bazel itself.\n\n```bash\nmise use --pin bazelisk@\u003Cversion>   # then: echo \"\u003Cbazel-version>\" > .bazelversion\n```\n\nWhen a trigger holds and you're migrating, follow the phased path in\n[`references\u002Fbazel-migration.md`](references\u002Fbazel-migration.md).\n\n## Templates\n\nCopy and adapt:\n\n- [`references\u002Fmise.toml`](references\u002Fmise.toml) — pinned `[tools]`, `[env]`,\n  `[tasks]`.\n- [`references\u002Fdevenv.nix`](references\u002Fdevenv.nix) — minimal fallback shell.\n",{"name":5,"description":7},"main","f92fca73134478305fd12b6f207db4ac71a1a901","skills\u002Fdeveloper-environment","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit","https:\u002F\u002Fgithub.com\u002Frahulmutt","2026-10-19 03:03:07",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add rahulmutt\u002Fdevkit --skill developer-environment",{"tool":36,"command":37},"bunx","bunx skills add rahulmutt\u002Fdevkit --skill developer-environment",{"tool":39,"command":40},"pnpm","pnpm dlx skills add rahulmutt\u002Fdevkit --skill developer-environment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fdeveloper-environment\u002FSKILL.md",true,[44,50,54,58],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fbazel-migration.md","REFERENCE","参考文档",1995,"https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fdeveloper-environment\u002Freferences\u002Fbazel-migration.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fdecision-tree.md",1298,"https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fdeveloper-environment\u002Freferences\u002Fdecision-tree.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fdevenv.nix",441,"https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fdeveloper-environment\u002Freferences\u002Fdevenv.nix",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fmise.toml",323,"https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fdeveloper-environment\u002Freferences\u002Fmise.toml",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M77MEJQ0MXKQJZMXBGAXWRVZ","writing-clean-code","Use when refactoring or restructuring code, splitting a file or module that has grown too large, deciding whether to extract a helper or inline it, naming things, removing dead or unused code, drawing module or package boundaries, handling errors, writing comments, applying DDD or hexagonal (ports and adapters) architecture, or checking a language's idiomatic style.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-clean-code\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M77MEG5ZPHCG2VZKHV885VPQ","using-devkit","Use when starting any conversation or new engineering task in a repo with devkit installed — establishes that devkit skills exist and must be checked before acting.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fusing-devkit\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77MECVQXHNQN0FQD62451G0","testing-practices","Use when writing, adding, or reviewing tests; choosing between unit, integration, snapshot\u002Fgolden, property, fuzz, mutation, e2e\u002FUI, or formal methods; when a test is flaky or the suite or CI is slow; or when deciding what runs in pre-commit, PR CI, or nightly.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Ftesting-practices\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M77ME7KX7BK4H37744MTG2J2","security-practices","Use when code touches a trust boundary — HTTP endpoints, webhooks, file uploads, auth, sessions, permissions, SQL or shell built from input, deserialization, service-to-service calls — when handling secrets, API keys, or .env files, on a CVE or vulnerability alert, when writing a threat model, or when choosing secret, SCA, SAST, or container scanners.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-practices\u002FSKILL.md",[],[],{"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":97,"publishedAt":19},"01M77ME3080TN2RA76XBGJ5WKV","navigable-codebases","Use when writing or updating a README, AGENTS.md, CLAUDE.md, GEMINI.md, ARCHITECTURE.md, or onboarding docs; when setting up a new repository; when adding or naming task-runner commands (mise tasks, Makefile, justfile, npm scripts); or when getting-started steps are missing, stale, or slow for newcomers.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fnavigable-codebases\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M77MDVH8D6Y5SPF72DXMYBS3","commits-and-releases","Use when writing commit messages or splitting work into commits; when cutting, versioning, or tagging a release; when editing a CHANGELOG or bumping a version number; when setting up or fixing release-please, semantic-release, or changesets; or when a release has the wrong version or is missing changelog entries.","https:\u002F\u002Fgithub.com\u002Frahulmutt\u002Fdevkit\u002Fblob\u002Fmain\u002Fskills\u002Fcommits-and-releases\u002FSKILL.md",[],[]]