Charlesjones Dev Claude Code Plugins Dev
charlesjones-dev-claude-code-plugins-dev is a Claude Code plugin for the Build phase that bundles twelve AI-powered development, audit, DevOps, and knowledge plugins for end-to-end workflow automation.
by charlesjones-dev · github.com/charlesjones-dev/claude-code-plugins-dev
Load a twelve-plugin Claude Code dev kit for audits, accessibility, Azure DevOps, knowledge capture, licensing checks, and agent workflow automation in one repo.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install charlesjones-dev-claude-code-plugins-dev@charlesjones-dev/claude-code-plugins-devBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:charlesjones-dev/claude-code-plugins-dev") and the paste-ready config with skillselion.get_install_config("plugin:charlesjones-dev/claude-code-plugins-dev").
What it does
charlesjones-dev-claude-code-plugins-dev is a Claude Code plugin collection—twelve plugins in one repository—that AI-powers large parts of an indie development workflow: accessibility checks, automated auditing, Azure DevOps integration, anti-pattern analysis, commit-and-PR assistance, dependency and license awareness, knowledge-base and Obsidian-friendly learnings harvest, humanizer and AI-generated-code detection, documentation generation, and broader agent mentoring patterns suggested by its keyword surface. Solo builders who want one install surface instead of hunting disparate skills treat it as journey-wide infrastructure: you can pull institutional memory during Idea-adjacent discovery, harden code during Ship review and security-minded passes, and keep Growth-ready documentation and content attribution honest. Complexity trends advanced because you must choose which plugins to enable and align them with your stack. The canonical Build → pm placement reflects PM-style governance over quality, knowledge, and delivery automation rather than a single frontend or backend task tool.
Highlights
- Twelve plugins in one charlesjones-dev/claude-code-plugins-dev marketplace-style bundle
- Coverage themes include a11y, code-quality audit, Azure DevOps, git commit/PR automation, and knowledge-base harvest
- AI-detection, licensing, and open-source notice tooling for attribution and compliance guardrails
- Obsidian-compatible institutional knowledge and lessons-learned capture for solo operators
- MCP, agent, and natural-language guided workflows across the full dev lifecycle
Why builders use it
Solo developers lose speed toggling between disconnected Claude extensions for reviews, DevOps, docs, licensing, and team memory.
After you register the bundle, you enable targeted plugins from one repo to audit code, automate git flows, integrate Azure DevOps, and capture learnings without reinstalling ad hoc tools each sprint.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 29 stars, 0 votes.
FAQ
Who is charlesjones-dev-claude-code-plugins-dev for?
It is for Claude Code power users who want a broad plugin kit covering audits, a11y, Azure DevOps, git automation, licensing, and knowledge capture from one repository.
When should I use charlesjones-dev-claude-code-plugins-dev?
Use it when you are building or maintaining a real codebase and need recurring agent help for review, compliance, documentation, and institutional memory—not for a one-off snippet.
How do I add charlesjones-dev-claude-code-plugins-dev to my agent?
Install the charlesjones-dev/claude-code-plugins-dev plugin bundle in Claude Code, enable only the plugins you need from the twelve-pack, and configure Azure or Obsidian integrations per each plugin’s docs.
Comments
Share how you use charlesjones-dev-claude-code-plugins-dev, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.