dev-tools

This skill should be used when the user asks 'what development tools are available', 'list dev plugins', 'what MCP servers can I use', 'enable code intelligence', 'what testing tools exist', or needs to discover development plugins like serena, playwright, or context7. Use this for general development tool discovery; use ds-tools for data science-specific tools.

6 stars

byedwinhu

View on GitHub Installation ↓

Best use case

dev-tools is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Teams using dev-tools should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/dev-tools/SKILL.md --create-dirs "https://raw.githubusercontent.com/edwinhu/workflows/main/skills/dev-tools/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/dev-tools/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How dev-tools Compares

Feature / Agent	dev-tools	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

AI Agents for Coding

Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.

Cursor vs Codex for AI Workflows

Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.

SKILL.md Source

# Available Development Tools

Plugins and skills for development workflows. For data science tools (WRDS, LSEG, notebooks), see `/ds-tools`.

## Code Intelligence Plugins

| Plugin | Description | Enable Command |
|--------|-------------|----------------|
| `serena` | Semantic code analysis, refactoring, symbol navigation | `claude --enable-plugin serena@claude-plugins-official` |
| `pyright-lsp` | Python type checking and diagnostics | `claude --enable-plugin pyright-lsp@claude-plugins-official` |
| `context7` | Up-to-date library/framework docs lookup | `claude --enable-plugin context7@claude-plugins-official` |

## Testing & Automation Plugins

| Plugin | Description | Enable Command |
|--------|-------------|----------------|
| `playwright` | Browser automation, E2E testing, screenshots | `claude --enable-plugin playwright@claude-plugins-official` |

## Built-in Iteration Primitives

| Command | Description |
|---------|-------------|
| `/goal` | Native cross-turn iteration with a separate small-fast-model evaluator. See `https://code.claude.com/docs/en/goal`. |
| `/loop` | Re-fire a prompt on a time interval (use for polling, not for goal-driven iteration). |

## When to Enable

- **serena**: Complex refactoring, finding symbol references, understanding large codebases
- **context7**: Need current docs for React, FastAPI, Next.js, etc.
- **playwright**: Testing web UIs, scraping, taking screenshots
- **pyright-lsp**: Python projects needing strict type checking

## Usage

```bash
claude --enable-plugin <plugin-name>  # Enable for current session
```

Related Skills

ds-tools

from edwinhu/workflows

This skill should be used when the user asks 'what data science tools are available', 'list data analysis plugins', 'what skills work with data', 'enable data science code intelligence', or needs to discover data-specific plugins and skills like wrds, lseg-data, gemini-batch, or data context skills. Use this for data science tool discovery; use dev-tools for general development tool discovery.

writing

from edwinhu/workflows

This skill should be used when the user asks to 'write a paper', 'start a writing project', 'draft an article', 'write about', 'brainstorm writing topics', 'gather sources for a paper', 'what should I write about', or needs the writing workflow entry point for any writing task.

writing-validate

from edwinhu/workflows

Validate draft sections cover all PRECIS claims before review.

writing-setup

from edwinhu/workflows

Internal skill for creating PRECIS.md, OUTLINE.md, and ACTIVE_WORKFLOW.md. Called after brainstorm sources are gathered.

writing-revise

from edwinhu/workflows

This skill should be used when the user asks to 'revise writing', 'fix review issues', 'polish draft', 'apply review feedback', 'complete writing workflow', or after /writing-review produces REVIEW.md with issues to fix.

writing-review

from edwinhu/workflows

Internal skill for hierarchical document review. Called by writing-validate after claim validation passes.

writing-precis-reviewer

from edwinhu/workflows

Internal skill used by writing-setup at exit gate. Dispatches a reviewer subagent to verify PRECIS.md quality before outlining. NOT user-facing.

writing-outline

from edwinhu/workflows

Internal skill for creating detailed section outlines. Called by /writing workflow after PRECIS and master OUTLINE are complete.

writing-outline-reviewer

from edwinhu/workflows

Internal skill used by writing-outline at exit gate. Dispatches a reviewer subagent to verify OUTLINE.md quality before drafting. NOT user-facing.

writing-lit-review

from edwinhu/workflows

Internal skill for literature review and source materialization. Called after brainstorm, before setup. NOT user-facing.

writing-legal

from edwinhu/workflows

Internal skill for academic legal writing. Loaded by /writing when style=legal. Based on Volokh's "Academic Legal Writing".

writing-handoff

from edwinhu/workflows

Create structured handoff document for writing workflow session pause/resume.