Skill UI

This skill guides the systematic triage of project issues and external pull requests (PRs). It moves development items through a defined state machine using roles (e.g., bug, enhancement) and states (e.g., ready-for-agent, wontfix). The process involves context gathering, cross-codebase verification, deep questioning (grilling), and generating comprehensive, agent-ready briefs or marking them for human implementation.

This skill enables users to upload local images, such as screenshots or before-and-after comparisons, directly to GitHub using the GitHub CLI. It bypasses the lack of a public image upload API by mimicking the web UI's internal attachment flow, generating canonical `user-attachments` URLs. These URLs can then be seamlessly embedded into Pull Requests, Issues, or comments from the terminal.

A portable CI gate designed to enforce Core Web Vitals (LCP, CLS, INP) budgets and category score floors on production frontend builds. It integrates into CI pipelines to automatically block pull requests if the performance metrics fall below defined Google standards, ensuring consistently fast and reliable user experiences.

This skill provides comprehensive pull request (PR) code reviews that go beyond simple syntax checks. It aggressively surfaces deep-rooted decay risks, architectural design smells, and maintainability issues. Findings are reported using a structured Symptom → Source → Consequence → Remedy framework, drawing insights from classic engineering principles. Ideal for reviewing complex or crucial code modules.

This advanced skill performs code review by simulating the documented engineering philosophies of historical figures (e.g., Linus Torvalds, Steve Jobs, Ken Thompson). It moves beyond generic AI findings by grounding critiques in specific, citable principles—such as 'good taste' or 'customer experience.' Ideal for high-stakes PRs, architectural reviews, and ensuring deep, pre-submission code hardening.

This skill performs a comprehensive, read-only, multi-agent review of a git diff or file scope. It launches four specialized sub-agents—covering Regression, Security, Performance, and Contracts—in parallel. The main agent then aggregates, filters, and summarizes critical findings, ensuring the code change is robust, secure, and maintainable. Ideal for pre-commit or Pull Request review workflows.

Code Health MCP provides structural maintainability feedback and design-level health scores, going beyond standard linting. It is crucial for AI-assisted coding workflows, allowing users to review code quality, verify score deltas after changes, and gate commits or pull requests to prevent codebase regression. Use it when refactoring, updating legacy modules, or ensuring the integrity of large diffs.

This tool analyzes Git diffs to provide comprehensive insights for Pull Requests (PRs) and large code changes. It calculates risk scores based on churn history and sensitive areas, classifies changes (e.g., feature, bugfix), recommends required reviewers, and provides detailed statistics. Use this before merging to assess code quality and minimize deployment risk.

A comprehensive guide to professional Git version control. It covers best practices for branching strategies (GitHub Flow, GitFlow, Trunk-Based), writing standardized commit messages using Conventional Commits, managing merges vs. rebases, and defining effective Pull Request workflows. Ideal for any development team looking to improve code collaboration and maintain a clean, traceable history.

A comprehensive pipeline designed for Laravel projects to ensure code quality and stability before deployment. It systematically executes environment checks, linting, static analysis, full testing with coverage, security audits, migration validation, and cache preparation. Essential for robust CI/CD pipelines and pre-Pull Request validation.

A comprehensive, multi-stage skill designed to simulate a professional Continuous Integration (CI) pipeline. It guides users through critical quality gates, including build verification, type checking, linting, running test suites (with coverage checks), security scanning for secrets, and final diff review. Use this skill before creating a Pull Request or finalizing any significant feature to ensure code robustness and adherence to best practices.

Provides a structured, multi-step workflow for addressing and fixing GitHub issues. This skill guides the user through the entire development lifecycle: understanding the bug, researching context, planning changes, implementing code, rigorous testing, and finally submitting a polished Pull Request using GitHub CLI commands.