Skill UI

Manages the complete lifecycle of GitHub issues using a structured, label-based state machine. This skill assists maintainers in triaging incoming reports, determining if an issue is a bug or enhancement, and moving it through defined states (e.g., needs info, ready for agent, wontfix). It ensures systematic workflow management for development projects.

Propose labels and categorize GitHub issues for maintainers without direct edits. Checks duplicates, verifies bug info, and drafts comments based on repository rules. Optimizes issue management workflow for googleapis/mcp-toolbox.

Guides external contributors to the Gentleman-Programming/gentle-ai repository through the strict issue-first workflow, honest PR bodies, chained-PR strategies, and verification protocols. Ensures compliance with contribution rules and maintainer expectations.

This skill creates, revises, or audits AGENTS.md files based on repository evidence and verified commands. It ensures coding agents understand the workflow without rediscovering it, preserving maintainer intent. It builds evidence maps from manifests and CI, scopes instructions correctly, and validates changes before handoff to prevent mistakes.

This skill enables repository maintainers to execute protected sweeps, batch PR merges, and scripted releases. It covers maintenance cycles, immutable distribution, and core checks. Use for CLI/MCP/Workbench changes or release work, excluding ordinary contributions. Includes rehearsal, verification, and publication workflows for GitHub and npm.

This workflow orchestrates review, tests, commits, and branch pushes using parallel agents to ensure changes move through validation into a pull request. It enforces repository policies, branch protection, and security checks before merging. Ideal for completed implementation work requiring strict validation, automated testing, and compliance with maintainer guidelines without bypassing safeguards.

This skill audits and repairs repository hygiene across artifacts, dependencies, CI, docs, Git state, and code-quality signals. It is used for repository maintenance, cleanup, health checks, or pre-release hardening. It ensures repository health through authorized repairs and protected workflows, validating changes before publishing via pull requests to maintain security and stability.