dev
v0.20.0Development workflow for Claude Code - six flat /dev commands, each self-contained, plus a worker and five review agents
By Victor RyabovLicense: MIT1 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 6 skill or MCP entries
- Source updated
- Aug 28, 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 plugin
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install dev@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/Villhard/nxsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/dev/.
Plugin files
├── .claude-plugin/plugin.json├── skills/bug/SKILL.md├── skills/commit/SKILL.md├── skills/exec/SKILL.md├── skills/plan/SKILL.md├── skills/review/SKILL.md└── skills/rnd/SKILL.md
Included Skills6
Investigate a bug to a confirmed root cause - the bug entry point. Use when handed a bug report, a tracker bug key/URL, stack trace, log, or observed misbehavior, before any fix is proposed.
Commit the current working changes - splits them into atomic commits with conventional messages. Use on any request to commit work made outside /dev:exec, and before running `git add` or `git commit` by hand.
Execute a planned ticket task by task and write the code, committing each finished task and marking the ticket resolved. Use after a plan is ready; add "no commits" to skip git.
Plan a ticket - decompose a spec, a root cause, or a request into sequenced tasks with checkboxes written into the ticket file. Use before executing non-trivial work, after a brainstorm or an investigation.
Review a diff with five parallel agents, verify every finding against the code, and report it. Add "fix" to apply the confirmed findings. Use after /dev:exec finishes a plan, or on any branch you want reviewed, including one you pulled from someone else's PR.
Think a request through to a spec and a set of tickets - the entry point for new work. Use to shape a fuzzy request, feature idea, or open question before planning.
Plugin manifests1
{
"name": "dev",
"description": "Development workflow for Claude Code - six flat /dev commands, each self-contained, plus a worker and five review agents",
"version": "0.20.0",
"author": {
"name": "Victor Ryabov",
"email": "[email protected]"
},
"keywords": [
"workflow",
"planning",
"review",
"development"
],
"license": "MIT",
"repository": "https://github.com/Villhard/nxs",
"homepage": "https://github.com/Villhard/nxs/tree/main/plugins/dev"
}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.
[dev on Agent Plugins Marketplace](https://pluginsmp.com/plugins/dev)