VIPER Metrics
Official@viper-metrics
Offers structured lifecycle management for GitHub repositories, encompassing issue investigation, feature planning, code implementation, and production release coordination.
Agent Skills by VIPER Metrics
Showing 11 vetted skills indexed across 1 GitHub repositories.
create-issue
Create well-documented GitHub issues through structured questions and code context.
feature-planner
Plan GitHub feature requests into implementation plans with architecture and testing steps.
implement-fix
Apply approved bug fix plans to codebases using git worktrees.
implement-feature
Implement approved feature plans using git worktrees and phased execution.
fix-planner
Generate a detailed fix plan from a bug investigation report.
investigate-bug
Investigate GitHub issues to identify root causes and affected files.
create-feature
Transform rough feature ideas into structured GitHub issues with technical context.
release-production
Coordinate repository state, changelog creation, and safe merges for production releases.
create-pr
Create GitHub pull requests from completed implementations via the GitHub CLI.
document-feature
Generates Word/PDF/HTML documents from templates and JSON data feeds.
close-pr
Close pull requests after testing and finalize issues, wiki docs, and worktrees.
Frequently Asked Questions About VIPER Metrics
FAQPage SchemaWhat specific tasks can be performed using VIPER Metrics?▼
VIPER Metrics enables end-to-end repository management, including investigating GitHub issues, generating technical fix plans, implementing features via git worktrees, managing pull requests, and coordinating production releases. It also supports generating technical documentation in Word, PDF, or HTML formats from structured data feeds.
Which personas benefit most from these capabilities?▼
Software engineers, technical leads, and release managers benefit from these capabilities. The system is designed for developers who need to maintain high-quality GitHub repositories, ensure consistent documentation, and manage the transition from bug investigation to production deployment through structured, repeatable processes.
What are the prerequisites for using these repository management functions?▼
Users require an active GitHub account with appropriate repository permissions to create issues, manage pull requests, and perform merges. The system relies on local git worktree support and access to the GitHub environment to execute implementation plans and finalize repository states.