agent-skills

Plugin agent-skills from marketplace javlonbek-sharipov in javlonbek-sharipov/agent-skills. Commands read from the repo's manifest — 12 days ago.

Skills (23)

• code-review

  Review a branch, PR, or local changes since a fixed point along two axes: Standards and Spec. Runs both reviews in parallel sub-agents and reports them side by side. Local review includes staged, unstaged, and untracked files. Use for code review, work in progress, or \"review since X\".

• codebase-design

  Shared vocabulary and checks for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary (module, interface, dept

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

• grill-with-docs

  A relentless interview to sharpen a plan or design, writing the docs as you go (GLOSSARY.md terms and ADRs). The entry point for work inside a repo.

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

• handoff

  Compact the current conversation into a handoff document for another agent to pick up.

• implement-spec

  Build a whole spec on one integration branch: parallel implementers, serialized verified merges, then a final code review.

• implement

  Implement one ticket, or one small piece of work, in this session: claim it, branch, build test-first, review, raise the PR if needed.

• improve-codebase-architecture

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

• pr

  Use when writing a PR body.

• prototype

  Build a throwaway prototype, in the app's own stack, to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look and feel like, on web, mobile or desktop.

• research

  Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

• retro

  Retrospective on a coding session: proposes changes to the agent's environment (checks, coding standards, steering files, tooling), not the code.

• setup-agent-skills

  Configure this repo for the skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once per repo, then commit the result so every collaborator's agent reads the same config.

• setup-verification

  Create or refresh a repo's recipe for verifying real user behavior.

• skill-guide

  Ask which skill or flow fits your situation. A router over the skills in this repo.

• tdd

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• to-spec

  Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

• to-tickets

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

• triage

  Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

• wayfinder

  Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

• wizard

  Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can pe

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Similar plugins