jvm-skills

Plugin jvm-skills from marketplace jvm-skills in jungvonmatt/agent-toolkit. Commands read from the repo's manifest — 6 days ago.

Skills (12)

• design-md

  Use when creating or refining a DESIGN.md, or when a design system must be extracted from a Figma file, live website, screenshot, or existing tokens file for use by agents.

• implement

  Use when executing an implementation plan under docs/plans/ (for example one written by start-ticket), or when asked to implement the next planned task or the whole plan ("auto").

• jvm-design

  Use when a project must adopt the Jung von Matt (JvM) CI 2026 design system, brand assets, or Carloschi fonts, or when asked to set up the JvM DESIGN.md in a project.

• pr-description

  Use when writing or updating a pull request or merge request description for the current branch, for GitHub, GitLab, or Bitbucket.

• pr-review

  Use when reviewing a pull request or merge request for merge readiness, regressions, security, performance, accessibility, or requirement compliance.

• repo-diagnostics

  Use when starting work on an unfamiliar codebase, onboarding to a repository, or auditing its technical health before reading any code, or when asked which files change or break most often, who knows the code (bus factor), or how commit velocity develops.

• scheduled-pr-review

  Use when running a recurring or unattended first-pass review of all open pull requests or merge requests, for example from a scheduled task, a cron job, or a loop that checks for new commits since the last run, on GitHub or GitLab.

• start-ticket

  Use when starting work on an existing Jira, Asana, Linear, GitHub, or GitLab issue — given its key or URL — that must become an implementation plan before any code is written.

• technical-writing

  Use when writing or updating code comments or doc comments (JSDoc, TSDoc, KDoc, Javadoc, docstrings), when documenting a project, API, or process for human readers (README, guide, reference, runbook, changelog, release notes), or when drafting a technical blog post.

• voiceover-check

  Use when a web change must be checked with a real screen reader on macOS — a ticket or definition of done asks for a VoiceOver or screen reader test, or the change adds or alters live regions, toasts, dialogs, focus moves, or accessible names, and you must know what VoiceOver actually announces and

• write-ticket

  Use when writing, refining, or structuring a ticket, issue, user story, or bug report for Jira, Linear, GitHub Issues, GitLab Issues, or Asana, or when a raw idea, bug report, or meeting notes must be turned into a development-ready ticket.

• writing-tests

  Use when writing, reviewing, or refactoring any automated test — unit, component, or integration — including whenever a test file (*.test.*, *.spec.*) or a component test is authored or changed.

Similar plugins