Agent skill

Leanspec Development

by codervisor in codervisor/leanspec

Development workflows, commands, publishing, CI/CD, changelog management, and contribution guidelines for LeanSpec.

MITAuto-check passedDevelopment

Install Leanspec Development

skills CLI
$ npx skills add codervisor/leanspec --skill leanspec-development -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install codervisor/leanspec leanspec-development --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/codervisor/leanspec.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/leanspec-development .claude/skills/leanspec-development && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
leanspec-development
GitHub stars
296
Token cost
~2.5k tokens
SKILL.md length
626 words
Files
11 (incl. references)
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Development workflows, commands, publishing, CI/CD, changelog management, and contribution guidelines for LeanSpec.

  • Works in 6 steps: Use pnpm — Never npm or yarn → DRY — Extract shared logic, avoid… → Test What Matters — Business logic and… → …
  • Contributing code
  • SKILL.md covers Quick Navigation, Core Principles, Commands and Critical Rules, plus 4 more sections
  • Calls pnpm, gh and git; reaches github.com and web.lean-spec.dev

What it does

Leanspec Development is an agent skill from codervisor/leanspec. Development workflows, commands, publishing, CI/CD, changelog management, and contribution guidelines for LeanSpec. Use when contributing code, fixing bugs, setting up dev environment, running tests or linting, working with the monorepo structure, looking up build/dev/test/publish/format/lint commands, preparing releases, publishing to npm, bumping versions, syncing package versions, testing dev builds, troubleshooting npm distribution, updating changelogs, triggering CI/CD workflows, monitoring build status…

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `references/CI-COMMANDS.md`, `references/CI-TROUBLESHOOTING.md` and `references/CI-WORKFLOWS.md`).

It sits in Development, covering Changelog and release notes, CI/CD and Linting and formatting. It works with npm and Rust. The repository describes itself as: Lightweight, flexible Spec-Driven Development (SDD) for modern AI-powered development. The licence is MIT.

When your agent uses it

  • Contributing code
  • Setting up dev environment
  • Working with the monorepo structure
  • Looking up build/dev/test/publish/format/lint commands

Example prompts

  • “/leanspec-development”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Use pnpm — Never npm or yarn
  2. DRY — Extract shared logic, avoid duplication
  3. Test What Matters — Business logic and data integrity, not presentation
  4. Leverage Turborepo — Smart caching (19s → 126ms builds)
  5. i18n is MANDATORY — Every user-facing string needs both en AND zh-CN (see I18N.md)
  6. Follow Rust Quality — All code must pass cargo clippy -- -D warnings

What it can do on your machine

Read from SKILL.md and the folder at commit ee122d6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • gh
    • git
    • cargo
    • npm
    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com
    • web.lean-spec.dev

    Also links to:

    • keepachangelog.com
    • semver.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Leanspec Development loads about 2.5k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 189 tokens; SKILL.md has 626 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~189
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from codervisor/leanspec at commit ee122d6, republished under its MIT licence (© codervisor). 626 words, ~2,546 tokens.

Download SKILL.mdSave it as .claude/skills/leanspec-development/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
leanspec-development
description
Development workflows, commands, publishing, CI/CD, changelog management, and contribution guidelines for LeanSpec. Use when contributing code, fixing bugs, setting up dev environment, running tests or linting, working with the monorepo structure, looking up build/dev/test/publish/format/lint commands, preparing releases, publishing to npm, bumping versions, syncing package versions, testing dev builds, troubleshooting npm distribution, updating changelogs, triggering CI/CD workflows, monitoring build status, debugging failed runs, managing artifacts, checking CI before releases, or researching AI agent runners. Triggers include any development, scripting, publishing, CI/CD, changelog, or runner research task in this project.
metadata.internal
true

LeanSpec Development Skill

Unified guide for all LeanSpec development: coding, commands, publishing, CI/CD, and runner research.

Quick Navigation

GoalReference
Mandatory rules & conventionsRULES.md
Changelog format & workflowChangelog (below)
i18n file locations & patternsI18N.md
Monorepo structure & packagesSTRUCTURE.md
Full release checklistPUBLISHING.md
npm distribution architectureNPM-DISTRIBUTION.md
Dev publishing workflowDEV-PUBLISHING.md
CI workflow detailsCI-WORKFLOWS.md
gh CLI command referenceCI-COMMANDS.md
CI troubleshootingCI-TROUBLESHOOTING.md
Runner ecosystem catalogrunners-catalog.md

Core Principles

  1. Use pnpm — Never npm or yarn
  2. DRY — Extract shared logic, avoid duplication
  3. Test What Matters — Business logic and data integrity, not presentation
  4. Leverage Turborepo — Smart caching (19s → 126ms builds)
  5. i18n is MANDATORY — Every user-facing string needs both en AND zh-CN (see I18N.md)
  6. Follow Rust Quality — All code must pass cargo clippy -- -D warnings

Commands

Daily Development
bash
pnpm install              # Install dependencies
pnpm dev                  # Start web UI + Rust HTTP server
pnpm dev:watch            # Same + auto-rebuild Rust on changes
pnpm dev:web              # Start web UI only
pnpm dev:desktop          # Start desktop app
pnpm build                # Build all TS packages
pnpm build:rust           # Build Rust (debug)
pnpm build:rust:release   # Build Rust (release)
pnpm typecheck            # ← NEVER SKIP before marking work complete
pnpm test                 # Run all tests
pnpm test:watch           # Watch mode
pnpm test:coverage        # With coverage
pnpm test:rust            # Rust tests only
pnpm format               # Format all code
pnpm cli                  # Run LeanSpec CLI
Validation
bash
pnpm pre-push             # Quick: typecheck + clippy
pnpm pre-release          # Full: build + typecheck + test + lint

⚠️ Always run pnpm typecheck before marking work complete.

Rust
bash
pnpm build:rust           # Debug build
pnpm build:rust:release   # Release build
pnpm check:rust           # Quick check without building
pnpm lint:rust            # Clippy with warnings as errors
pnpm format:rust          # Format Rust code
pnpm format:rust:check    # Check Rust formatting

# Low-level
cargo build --manifest-path rust/Cargo.toml
node scripts/copy-rust-binaries.mjs --debug
Documentation
bash
pnpm docs:dev             # Start docs dev server
pnpm docs:build           # Build docs site
Desktop
bash
pnpm dev:desktop          # Start desktop app in dev mode
cd packages/desktop
pnpm bundle:linux         # Debian package
pnpm bundle:macos         # DMG
pnpm bundle:windows       # NSIS installer

Critical Rules

Rules enforced by hooks or CI:

  1. Light/Dark Theme — ALL UI must support both themes
  2. i18n — Update BOTH en and zh-CN → I18N.md ⚠️ commonly forgotten
  3. Regression Tests — Bug fixes MUST include failing-then-passing tests
  4. Rust Quality — Must pass cargo clippy -- -D warnings
  5. Rust Params Structs — Functions with >7 args must use a params struct (enforced by clippy.toml)
  6. Use shadcn/ui — No native HTML form elements
  7. cursor-pointer — All clickable items must use cursor-pointer

See RULES.md for complete requirements.


Publishing & Releases

bash
# 1. Update version (root only)
npm version patch  # or minor/major

# 2. Sync all packages
pnpm sync-versions

# 3. Validate everything
pnpm pre-release

# 4. Commit and push with tags
git add .
git commit -m "chore: release vX.X.X"
git push --follow-tags

# 5. Create GitHub Release (triggers publish workflow)
gh release create vX.X.X --title "vX.X.X" --notes "Release notes here"
Development Release
bash
# Publish dev version via GitHub Actions
gh workflow run publish.yml --field dev=true

# Dry run (validates without publishing)
gh workflow run publish.yml --field dev=true --field dry_run=true

# Install and test
npm install -g lean-spec@dev
lean-spec --version
Version Management
  • Root package.json is the single source of truth for versions
  • pnpm sync-versions propagates to all packages (including Rust crates)
  • CI automatically validates version alignment
  • Never manually edit package versions — use npm version + pnpm sync-versions
Distribution Architecture

LeanSpec uses optional dependencies for platform-specific Rust binaries:

TypePackages
Main (published)lean-spec, @leanspec/mcp, @leanspec/ui
Platform (published)@leanspec/cli-{platform}, @leanspec/mcp-{platform} (5 platforms each)
Internal (not published)@leanspec/desktop, @leanspec/ui-components

⚠️ Platform packages MUST be published before main packages. The CI workflow handles this automatically.

See PUBLISHING.md and NPM-DISTRIBUTION.md for details.


Changelog

Update CHANGELOG.md following Keep a Changelog format and Semantic Versioning.

Discovering Changes
bash
# Commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline

# Files changed since last release
git diff $(git describe --tags --abbrev=0)..HEAD --stat
Entry Format

Only include shipped/implemented changes — not planned specs, drafts, or WIP.

Add under ## [Unreleased] using these categories: Added, Changed, Fixed, Deprecated, Removed, Security, Technical.

markdown
- **Feature Name** ([spec 123](https://web.lean-spec.dev/specs/123)) - Brief description
  - Sub-bullet with implementation details
Show full SKILL.md (272 more words)Show less
Writing Style
  1. Bold feature name followed by description
  2. Link related specs when applicable
  3. Present tense — "Adds support for..." not "Added"
  4. Be specific — include command names, flag names, component names
  5. Group related changes under single bullet with sub-bullets
  6. Include breaking changes with Breaking: prefix
Creating a Release
  1. Move entries from [Unreleased] to new version: ## [X.Y.Z] - YYYY-MM-DD
  2. Add release link at bottom: [X.Y.Z]: https://github.com/codervisor/lean-spec/releases/tag/vX.Y.Z

CI/CD (GitHub Actions)

All workflow interactions use the gh CLI. Check status before triggering new runs; minimum 30s between polls.

Available Workflows
WorkflowFileTriggersPurpose
CIci.ymlpush, PR to mainBuild, test, lint (Node.js + Rust)
Publishpublish.ymlrelease, manualPublish to npm (all platforms)
Desktop Builddesktop-build.ymlpush, PR, manualBuild Tauri desktop apps
Copilot Setupcopilot-setup-steps.ymlpush, PR, manualSetup environment for Copilot agent
Quick Reference
bash
# Check status
gh run list --limit 10
gh run list --workflow ci.yml --limit 5
gh run view <run-id>
gh run watch <run-id>

# Trigger
gh workflow run ci.yml
gh workflow run publish.yml --field dev=true

# Debug failures
gh run view <run-id> --log-failed
gh run rerun <run-id> --failed

# Artifacts
gh run download <run-id>
gh run download <run-id> --name ui-dist

See CI-WORKFLOWS.md, CI-COMMANDS.md, and CI-TROUBLESHOOTING.md for details.


Runner Research

Research AI agent runners to keep LeanSpec's runner registry current as the ecosystem evolves.

Workflow
  1. Read current state: rust/leanspec-core/src/sessions/runner.rs (RunnerRegistry::builtins())
  2. Read catalog: runners-catalog.md
  3. Research via web_search: Config format changes, CLI changes, new env vars, new capabilities, deprecations, new runners
  4. Compare & identify gaps: Cross-reference findings against registry
  5. Report: Minor updates → update catalog directly; major changes → create a spec
Runner Tiers
  1. Tier 1 (high priority): Claude Code, Copilot, Cursor, Windsurf, Codex, Gemini
  2. Tier 2 (medium): Kiro, Amp, Aider, Goose, Continue, Roo Code
  3. Tier 3 (monitor): Droid, Kimi, Qodo, Trae, Qwen Code, OpenHands, Crush, CodeBuddy, Kilo, Augment
Key Source Files
FilePurpose
rust/leanspec-core/src/sessions/runner.rsRunner registry with detection config
schemas/runners.jsonJSON schema for custom runner config
packages/cli/templates/_shared/agents-components/AGENTS.md template components

© codervisor, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references) in .agents/skills/leanspec-development of codervisor/leanspec.

  • SKILL.md
  • references/CI-COMMANDS.md
  • references/CI-TROUBLESHOOTING.md
  • references/CI-WORKFLOWS.md
  • references/DEV-PUBLISHING.md
  • references/I18N.md
  • references/NPM-DISTRIBUTION.md
  • references/PUBLISHING.md
  • references/RULES.md
  • references/STRUCTURE.md
  • references/runners-catalog.md

Open the folder on GitHubat commit ee122d6

Compare with similar skills

Leanspec Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Leanspec Development compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Leanspec Development this skillcodervisor/leanspec296—~2.5kAutomated safety check: PassMIT
Automate npm Releasejd-solanki/slidev-theme-dracula161—~626Automated safety check: PassNone
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0
Worktrunk Release Workflowmax-sixty/worktrunk8.9k—~6.9kAutomated safety check: PassCustom licence
Ccb GitHubSeemSeam/claude_codex_bridge3.5k—~4.9kAutomated safety check: PassCustom licence
Cut Releasedelexw/claude-code-trace3761 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Automate npm Release

    jd-solanki/slidev-theme-dracula

    Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and…

    161 GitHub stars~626 tokensUpdated 3 mo ago
    DevelopmentAuto-check passed
  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Worktrunk Release Workflow

    max-sixty/worktrunk

    Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

    8.9k GitHub stars~6.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Ccb GitHub

    SeemSeam/claude_codex_bridge

    Maintain this CCB project's GitHub-facing release and npm publication surface.

    3.5k GitHub stars~4.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Cut Release

    delexw/claude-code-trace

    Cuts a new versioned release of claude-code-trace end-to-end without asking any questions.

    376 GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Release

    xin2017338/lynx-proxy

    Publish a new release version of Lynx Proxy. An agent skill from xin2017338/lynx-proxy.

    502 GitHub stars~1.1k tokensUpdated 22 days ago
    DevelopmentAuto-check passed

More from codervisor/leanspec

  • Leanspec

    codervisor/leanspec

    The spec-coding methodology for AI-assisted development. An agent skill from codervisor/leanspec.

    296 GitHub stars~1.8k tokensUpdated 4 mo ago
    Auto-check passed
  • Leanspec Dev Process

    codervisor/leanspec

    The end-to-end spec-issue-driven dev loop for lean-spec — spec → branch → implement → PR → merge → closure.

    296 GitHub stars~3.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Leanspec PR Lifecycle

    codervisor/leanspec

    Manage a lean-spec PR after it's been pushed — spec-issue linking, CI triage, review-comment discipline, merge-conflict recovery on open PRs, webhook subscription, and CHANGELOG follow-through on…

    296 GitHub stars~3.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Leanspec Pre Push

    codervisor/leanspec

    Run before pushing code to the lean-spec repo to catch what reviewers and CI will catch later, and confirm the branch has a linked spec issue in a valid state.

    296 GitHub stars~2.5k tokensUpdated 4 mo ago
    Auto-check passed
  • Watch CI

    codervisor/leanspec

    Watch GitHub Actions CI status for the current commit until completion.

    296 GitHub stars~724 tokensUpdated 4 mo ago
    Auto-check: notes

Works with

Categories

Questions about Leanspec Development

What does Leanspec Development do?

Development workflows, commands, publishing, CI/CD, changelog management, and contribution guidelines for LeanSpec. Leanspec Development is an agent skill from codervisor/leanspec. Development workflows, commands, publishing, CI/CD, changelog management, and contribution guidelines for LeanSpec.

When should I use Leanspec Development?

Leanspec Development fits situations like: contributing code; setting up dev environment; working with the monorepo structure; looking up build/dev/test/publish/format/lint commands.

How do I install Leanspec Development in Claude Code?

Run `npx skills add codervisor/leanspec --skill leanspec-development -a claude-code`. Or copy the skill folder (.agents/skills/leanspec-development in codervisor/leanspec) into .claude/skills/leanspec-development in your project. Claude Code loads it when a task matches its description.

How do I install Leanspec Development in Codex?

Run `npx skills add codervisor/leanspec --skill leanspec-development -a codex`. Or copy the skill folder (.agents/skills/leanspec-development in codervisor/leanspec) into .agents/skills/leanspec-development in your project. Codex loads it when a task matches its description.

Can I use Leanspec Development in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codervisor/leanspec --skill leanspec-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/leanspec-development, .gemini/skills/leanspec-development, .github/skills/leanspec-development and .opencode/skills/leanspec-development in your project.

What does Leanspec Development need to run?

Going by SKILL.md and its folder, Leanspec Development needs the command-line tools its instructions call (pnpm, gh, git, cargo, npm and node). Our summary lists: Node.js.

Does Leanspec Development access the network?

SKILL.md names 4 domains. In commands or code: github.com and web.lean-spec.dev; the agent is likely to contact these when it follows the instructions. As links in the text: keepachangelog.com and semver.org. This is read from the text; nothing was executed.

Is Leanspec Development safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Leanspec Development use?

Leanspec Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Leanspec Development use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.

What are the alternatives to Leanspec Development?

Skills that share tags, products or a category with Leanspec Development: Automate npm Release (jd-solanki/slidev-theme-dracula, 161 stars), Cutting A Release (TriliumNext/Trilium, 38k stars), Worktrunk Release Workflow (max-sixty/worktrunk, 8.9k stars) and Ccb GitHub (SeemSeam/claude_codex_bridge, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Leanspec Development?

codervisor (a GitHub organization) maintains it in codervisor/leanspec, which has 296 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on May 20, 2026.

Source: codervisor/leanspec on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.