Agent Plugins Marketplace
← All plugins

dev-flow

v6.15.0

Code review, fixes, commits, release flows, and linting for development workflows

Claude Code6 Skills

By Alexei LedenevLicense: MIT36 GitHub starsUpdated 1 hour ago

Directory evidence

Runtimes
Claude Code
Parsed components
6 skill or MCP entries
Source updated
Sep 30, 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 dev-flow for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install dev-flow-4@agent-plugin-marketplace

Paste 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/alexei-led/cc-thingz

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is dist/claude/dev-flow/.

Plugin files

dist/claude/dev-flow/
├── .claude-plugin/plugin.json
├── skills/committing-code/SKILL.md
├── skills/documenting-code/SKILL.md
├── skills/fixing-code/SKILL.md
├── skills/improving-tests/SKILL.md
├── skills/releasing-code/SKILL.md
└── skills/reviewing-code/SKILL.md

Included Skills6

committing-codeskills/committing-code/SKILL.md

Create normal git commits with logical grouping. Use when committing, saving changes, creating commits, or grouping work into commits. NOT for amending, rebasing, force-pushing, or rewriting history.

documenting-codeskills/documenting-code/SKILL.md

Write, rewrite, or update project docs from implementation facts - README front pages, user guides, configuration references, architecture docs, evaluations, agent instructions, and code comments. Use when docs are stale after a change, or when a doc set must become clear, visual, and consistent with the code. NOT for release preparation or release notes (use releasing-code), external library docs (looking-up-docs), scoring instruction files (reviewing-instructions), or ADRs unless explicitly requested.

fixing-codeskills/fixing-code/SKILL.md

Fix code defects with a reproducible feedback loop, root-cause diagnosis, minimal patch, regression test, and clean verification. Use when debugging, diagnosing, or resolving lint/test/build failures. NOT for test-suite cleanup without a production bug (use improving-tests), or code review findings without fixes (use reviewing-code).

improving-testsskills/improving-tests/SKILL.md

Improve test design, speed, and coverage with behavior-focused tests, useful seams, characterization tests, TDD, and test refactoring. Use when improving tests, optimizing slow suites, adding coverage, refactoring brittle tests, removing test waste, or working test-first. NOT for fixing production bugs (use fixing-code), or reviewing non-test code quality (use reviewing-code).

releasing-codeskills/releasing-code/SKILL.md

Prepare, publish, or repair a software release and write its release notes. Use for cutting a versioned release or editing release notes. NOT for updating an installed package, publishing articles, or discussing a release; for general documentation use documenting-code.

reviewing-codeskills/reviewing-code/SKILL.md

Use when reviewing changed code, PRs, diffs, or specific files. Finds evidence-backed defects in security, correctness, tests, reliability, performance, maintainability, and docs. Supports quick, standard, deep, team, and external-review modes, plus a simplify mode for over-engineering and "what can we delete" reviews. NOT for repo-wide architecture review, general codebase exploration, fixing issues (use fixing-code), or improving tests without a code review (use improving-tests).

Plugin manifests1

dist/claude/dev-flow/.claude-plugin/plugin.json
{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "author": {
    "name": "Alexei Ledenev"
  },
  "description": "Code review, fixes, commits, release flows, and linting for development workflows",
  "homepage": "https://github.com/alexei-led/cc-thingz",
  "keywords": [
    "development",
    "review",
    "testing"
  ],
  "license": "MIT",
  "name": "dev-flow",
  "repository": "https://github.com/alexei-led/cc-thingz",
  "version": "6.15.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.

[dev-flow on Agent Plugins Marketplace](https://pluginsmp.com/plugins/dev-flow-4)