base-dev-kit
v0.1.0Honesty and security rules always applied, plus on-demand skills for clean code, git workflow, test-driven development, dependency management, and documentation — applicable to any language or stack.
By Artsiom MurashkoLicense: MIT0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Oct 2, 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 base-dev-kit for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install base-dev-kit@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/Ksarelto/dev-AI-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is base-dev-kit/.
Plugin files
├── .claude-plugin/plugin.json├── skills/clean-code/SKILL.md├── skills/dependencies/SKILL.md├── skills/documentation/SKILL.md├── skills/git-workflow/SKILL.md└── skills/tdd/SKILL.md
Included Skills5
Clean code principles — naming, function size, complexity, magic values, dead code, and comment discipline. Use when writing new code, refactoring, or reviewing a diff for readability/maintainability issues. Applies to any language.
Dependency and versioning policy — evaluating a new package, lockfile discipline, semver, upgrade cadence, and pinning. Use when adding a dependency, upgrading one, or deciding how to version a published package. Applies to any language.
When documentation is required vs. skipped — READMEs, ADRs, and docstrings — and how to sweep .md/.txt/.mdc/.yaml/.json files for stale values after a feature or approach change. Use when adding/updating a README, deciding whether a decision needs an ADR, deciding whether a function needs a docstring, or finishing a change whose details shifted mid-development. Applies to any language.
Git workflow standards — commit message format, branch naming, atomic commits, PR conventions, and code review etiquette. Use when creating a commit, opening a branch/PR, or leaving code review comments.
Test-driven development — red/green/refactor, reproduction tests for bug fixes, the test pyramid and test sizes, what to test, mocking discipline, naming, and anti-patterns. Use when implementing new behavior, fixing a bug, or structuring/reviewing a test suite. Applies to any language.
Plugin manifests1
{
"name": "base-dev-kit",
"displayName": "Base Dev Kit",
"description": "Honesty and security rules always applied, plus on-demand skills for clean code, git workflow, test-driven development, dependency management, and documentation — applicable to any language or stack.",
"version": "0.1.0",
"author": {
"name": "Artsiom Murashko"
},
"license": "MIT",
"keywords": [
"clean-code",
"security",
"git",
"testing",
"tdd",
"honesty",
"universal",
"dependencies",
"documentation"
],
"category": "productivity",
"rules": "./rules/",
"skills": "./skills/"
}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.
[base-dev-kit on Agent Plugins Marketplace](https://pluginsmp.com/plugins/base-dev-kit)