developer-tooling
v0.1.2Developer-tooling team — the BUILD-TOOLING layer for monorepo & build-systems engineering. agents (build-systems-architect, monorepo-engineer) covering monorepo tooling (Nx, Turborepo, Bazel/Buck2, Moon, pnpm/yarn/npm workspaces, Lerna), build performance & remote/content-addressable caching, task graphs and affected/since-only builds, dependency & package management (version policy, lockfile hygiene, renovate/dependabot, supply-chain hygiene: SBOM/provenance/pinning), and code-generation/scaffolding. skills (choose-monorepo-tooling, optimize-build-and-cache, manage-dependencies), Mermaid-backed knowledge docs (monorepo-tooling decision tree, build-caching & performance), and runbook templates. Seams: CI/CD pipelines → devops-cicd; service code → backend/frontend-engineering; containers/IaC → the cloud plugins. House line: measure before you migrate; cache correctness before cache speed. Requires ravenclaude-core@>=0.7.0.
By Matt CorbettLicense: MIT7 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install developer-tooling for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install developer-tooling@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mcorbett51090/RavenClaudeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/developer-tooling/.
Plugin files
├── .claude-plugin/plugin.json├── skills/choose-monorepo-tooling/SKILL.md├── skills/manage-dependencies/SKILL.md└── skills/optimize-build-and-cache/SKILL.md
Included Skills3
Pick the right monorepo/build tool and package manager for a described repo by traversing the monorepo-tooling decision tree (language mix → scale → hermeticity need → tool), then return the recommended tool, the package-manager pick, the tradeoffs, and an explicit list of what NOT to adopt yet. Reach for this when the user asks 'which monorepo tool?' or 'should we adopt Nx/Turborepo/Bazel?'. Used by `build-systems-architect` (primary).
Set and enforce dependency & package management across a monorepo: version policy (single-version vs independent), lockfile hygiene (commit + freeze in CI), automated batched upgrades (renovate/dependabot), supply-chain hygiene (SBOM, provenance/SLSA, digest pinning), and staged cross-repo upgrades. Reach for this when the user asks 'how do we manage versions/lockfiles?' or 'upgrade X safely across the monorepo'. Used by `monorepo-engineer` (primary).
Diagnose and fix a slow build by measuring the task graph and cache-hit rate, auditing cache CORRECTNESS (input-hash completeness, hermeticity leaks) before any speed tuning, then applying the highest-leverage fix (affected-only, remote cache, parallelism, splitting the long pole). Reach for this when the user says 'the build is slow' or 'is remote caching worth it / even correct?'. Used by `build-systems-architect` (primary).
Plugin manifests1
{
"name": "developer-tooling",
"version": "0.1.2",
"description": "Developer-tooling team — the BUILD-TOOLING layer for monorepo & build-systems engineering. agents (build-systems-architect, monorepo-engineer) covering monorepo tooling (Nx, Turborepo, Bazel/Buck2, Moon, pnpm/yarn/npm workspaces, Lerna), build performance & remote/content-addressable caching, task graphs and affected/since-only builds, dependency & package management (version policy, lockfile hygiene, renovate/dependabot, supply-chain hygiene: SBOM/provenance/pinning), and code-generation/scaffolding. skills (choose-monorepo-tooling, optimize-build-and-cache, manage-dependencies), Mermaid-backed knowledge docs (monorepo-tooling decision tree, build-caching & performance), and runbook templates. Seams: CI/CD pipelines → devops-cicd; service code → backend/frontend-engineering; containers/IaC → the cloud plugins. House line: measure before you migrate; cache correctness before cache speed. Requires ravenclaude-core@>=0.7.0.",
"author": {
"name": "Matt Corbett"
},
"homepage": "https://github.com/mcorbett51090/RavenClaude",
"license": "MIT",
"keywords": [
"monorepo",
"build-systems",
"nx",
"turborepo",
"bazel",
"remote-cache",
"task-graph",
"pnpm-workspaces",
"dependency-management",
"supply-chain-security",
"renovate",
"code-generation"
],
"requires": {
"plugins": [
"ravenclaude-core@>=0.7.0"
]
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[developer-tooling on Agent Plugins Marketplace](https://pluginsmp.com/plugins/developer-tooling)