Pavel Malove
Community@PVMalove
Pavel Malove maintains a 33-skill agent harness for software project orchestration, covering issue triage, ticket decomposition, code review, TDD, and delivery analytics.
Agent Skills by Pavel Malove
Showing 33 vetted skills indexed across 1 GitHub repositories.
PVMaloveintegrate-project
Audit an existing codebase and integrate the agent harness without disrupting current conventions.
PVMalovestart-project
Initialize new projects and assemble portable agent harnesses from confirmed manifests.
PVMaloveqa-gate
Runs the project's configured lint, typecheck, and test commands and reports a bounded pass/fail summary.
PVMalovewayfinder
Plan large efforts as decision-ticket maps on an issue tracker.
PVMaloveto-pull-requests
Opens a pull request for a pushed issue branch after validating branch state and QA evidence.
PVMaloveto-guide
Generates step-by-step implementation guides with ready-to-paste AI IDE prompts for human-coded tickets.
PVMalovecode-review
Reviews a git diff against coding standards and the originating spec using parallel sub-agents.
PVMaloveto-tickets
Breaks plans and specs into tracer-bullet tickets with blocking edges and publishes them to an issue tracker.
PVMaloveask-matt
Routes user situations to the appropriate skill or workflow in the repository.
PVMaloveto-spec
Synthesizes conversation context into a specification and publishes it as a GitHub epic issue.
PVMalovetriage
Move issues and external PRs through a label-based triage state machine.
PVMalovedelivery-stats
Generates delivery cost and token usage reports for completed epics and tickets.
PVMalovegrill-with-docs
Runs a structured interview to sharpen plans while generating ADRs and a glossary.
PVMaloveimplement
Coordinates one backend ticket through architect, developer, review, QA, and publish dispatches.
PVMalovesetup-labels
Creates and updates GitHub repository labels from the triage taxonomy using the gh CLI.
PVMalovegrill-me
Runs a structured interview session to sharpen a plan or design.
PVMalovegrilling
Stress-tests plans and decisions through structured rounds of interrogative questions.
PVMalovefast-implement
Implements a ticket in one session without coordinator approval gates.
PVMaloveresearch
Investigates questions against primary sources and saves cited findings as Markdown files.
PVMalovedomain-modeling
Build and maintain a project domain model with CONTEXT.md glossaries and ADR records.
PVMalovesetup-matt-pocock-skills
Configure a repository's issue tracker, triage labels, and domain doc layout for engineering skills.
PVMalovediagnosing-bugs
Diagnose hard bugs and performance regressions through a six-phase feedback-loop workflow.
PVMalovewizard
Generate interactive bash wizards that walk humans through manual setup procedures.
PVMaloveimprove-codebase-architecture
Scan a codebase for shallow modules and present deepening refactors as a visual HTML report.
Frequently Asked Questions About Pavel Malove
FAQPage SchemaWhat tasks can I accomplish with Pavel Malove's skill collection?▼
You can start or integrate projects into an agent harness, triage issues, convert specs into tickets, coordinate backend implementation through architect-developer-review-QA handoffs, run code reviews against standards and specs, practice TDD, diagnose bugs, resolve merge conflicts, and collect delivery statistics per epic.
Who is the target audience for these skills?▼
Software engineers and technical leads managing repositories with issue trackers. The skills suit developers who want structured spec-to-ticket decomposition, parallel code review sub-agents, domain modeling with ADRs and glossaries, and manual implementation guides for AI IDEs like Cursor or Copilot Chat.
How do I set up and run these skills in a repository?▼
Run setup-matt-pocock-skills once to configure the issue tracker, triage label vocabulary, and domain doc layout, then run setup-labels to create GitHub labels. Use start-project for new repos or integrate-project for existing codebases, then invoke individual skills like triage, implement, or qa-gate.
What prerequisites do these skills require?▼
A repository with a configured issue tracker (GitHub), the harness files including AGENTS.md and .harness/project.json defining lint, typecheck, and test commands, and the label vocabulary from docs/agents/triage-labels.md. The qa-gate skill specifically reads commands from .harness/project.json.
How does the code review skill evaluate changes?▼
The code-review skill examines changes since a fixed point such as a commit, branch, tag, or merge-base along two axes: Standards, checking documented coding conventions, and Spec, verifying the code matches the originating issue. Both reviews run in parallel sub-agents and report side by side.