esp-skills

Plugin esp-skills from marketplace esp in e-stpierre/skills. Commands read from the repo's manifest — 3 days ago.

Skills (18)

• esp-create-skill

  Create a new Claude Code skill following best practices and guidelines

• esp-config

  Initialize, show, get, set, and validate esp-skills configuration

• esp-branch

  Create a branch with standardized naming convention

• esp-commit

  Commit changes with a structured message

• esp-pr

  Create a pull request with contextual title and description

• esp-await-review

  Wait in the background for bot reviews of a pull request's head commit, then report

• esp-fix-review

  Fix, reply to, or defer PR review comments and failing CI checks, or esp-review findings

• esp-merge

  Merge a pull request under objective conditions, with the method the repository allows

• esp-qna

  Answer questions clearly and concisely without modifying the codebase

• esp-rubberduck

  Clarify ideas through discussion, questions, and suggestions based on conversation context

• esp-review

  Code review in a fresh context, returning verified findings classified for a fixer. Use when asked to review local changes, a branch, a ref range or a pull request.

• esp-analyze

  Severity-ranked codebase analysis report for one issue type. Use to audit the codebase for bugs, technical debt, documentation drift, security vulnerabilities, or style inconsistencies.

• esp-build

  Build a plan milestone by milestone, one verified commit per milestone

• esp-go-light

  Take a small task from request to merged pull request in one session, or escalate to esp-go

• esp-go

  Run a feature from request to merged pull request, with phase subagents and a commit per milestone

• esp-plan

  Implementation plan as parseable milestones in a run directory. Use to plan a feature, bug fix or chore before building it, or to amend the remaining milestones of an existing plan.

• esp-recap

  Sourced recap of past esp-skills and harness runs. Use to summarize what runs did, to report their risky decisions and critical findings, or to answer why a past run did something.

• esp-markdown

  MUST be used before creating, editing, or reviewing any markdown (.md) file. Enforces project formatting conventions and non-auto-fixable lint rules.

Subagents (3)

• esp-builder

  Implements one plan milestone or one set of review fixes as exactly one commit

• esp-reviewer

  Reviews a diff in a fresh context and returns verified, classified findings

• esp-verifier

  Re-runs gates and checks acceptance criteria independently, without changing code

Similar plugins