toolchain-experts
v0.1.0Five expert reviewers that RUN the project's own static analysis instead of reciting a best-practice checklist: php-expert (phpstan, psalm, phpcs, rector), ts-expert (tsc, eslint, biome, oxlint), react-expert (the hook rules), vue-expert (vue-tsc, eslint-plugin-vue) and ui-expert (stylelint, pa11y, lighthouse-ci, axe). A detect-analyzers.sh mechanism reports which tool is configured, which one CI actually enforces, what the baseline already forgives and which rules are switched off — so the headline finding is the analyzer's blind spot, which no remembered rubric can produce. Read-only; fixes route to the existing workers.
By Ivan-WG1 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 0 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 toolchain-experts for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install toolchain-experts@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/galaykos/cc-marketplaceClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/toolchain-experts/.
Plugin files
└── .claude-plugin/plugin.json
Plugin manifests1
{
"name": "toolchain-experts",
"version": "0.1.0",
"description": "Five expert reviewers that RUN the project's own static analysis instead of reciting a best-practice checklist: php-expert (phpstan, psalm, phpcs, rector), ts-expert (tsc, eslint, biome, oxlint), react-expert (the hook rules), vue-expert (vue-tsc, eslint-plugin-vue) and ui-expert (stylelint, pa11y, lighthouse-ci, axe). A detect-analyzers.sh mechanism reports which tool is configured, which one CI actually enforces, what the baseline already forgives and which rules are switched off — so the headline finding is the analyzer's blind spot, which no remembered rubric can produce. Read-only; fixes route to the existing workers.",
"author": {
"name": "Ivan-WG",
"email": "[email protected]"
},
"keywords": [
"review",
"tooling",
"quality",
"frontend",
"backend"
]
}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.
[toolchain-experts on Agent Plugins Marketplace](https://pluginsmp.com/plugins/toolchain-experts)