Skill UI

This skill generates user-friendly, public-facing release notes (changelogs) for App Stores. It analyzes the raw Git history since the last tag, intelligently filtering out internal commits (like refactors, CI updates, or build scripts) and grouping visible changes into concise, benefit-focused bullet points suitable for a "What's New" section.

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 guide to disciplined version control using Git. It outlines best practices for atomic commits, descriptive message formatting (feat, fix, refactor), adopting trunk-based development, and managing feature branches. Use this whenever making code changes, committing, or coordinating complex work streams to ensure code stability and traceability.

This tool generates highly standardized and ultra-compressed commit messages following the Conventional Commits specification. It ensures that commits are concise, professional, and adhere to strict formats (e.g., type(scope): summary). It intelligently generates a body only when the context (like breaking changes or complex reasoning) requires it, significantly reducing noise and maintaining a clean, clear project history.

This workflow guides developers through generating standardized, descriptive commit messages using the Conventional Commits specification. It provides a structured XML template (including type, scope, description, body, and footer) and integrates directly into the Git workflow, ensuring project history is clean, traceable, and machine-readable. Ideal for maintaining large, collaborative codebases.

Intelligently executes git commit by adhering to the Conventional Commits specification. The tool analyzes the staged or working directory diff to automatically detect the change type (e.g., feat, fix, docs), the affected scope, and generates a standardized, semantic commit message. This ensures your project history remains clean, readable, and compliant with best development practices. Ideal for maintaining robust version control.

A comprehensive methodology for pinpointing the root cause of complex bugs, regressions, or unexpected behavior in large codebases. Techniques include binary search debugging, Git bisect for tracking regressions across commits, strategic data/control flow logging, component isolation, and advanced breakpoint strategies (conditional breakpoints, watch expressions). Ideal for scenarios where the bug source is unclear or difficult to reproduce.

This guide provides a comprehensive framework for adopting Conventional Commits using Mandarin Chinese. It details rules for commit types (feat, fix, perf, etc.), structuring the subject, body, and footer messages. Furthermore, it covers integrating automated tools like husky, commitlint, and conventional-changelog to enforce standardized, professional, and traceable commit workflows for Chinese development teams.

A comprehensive guide providing best practices for Git workflows, covering adaptation strategies for major Chinese platforms (Gitee, Coding.net, etc.), branch naming conventions, standardized commit messaging (Chinese Conventional Commits), and CI/CD integration across various domestic environments. Helps streamline development processes for Chinese teams.

Transforms raw calendar data (ICS/JSON) into actionable development workflows. This skill automatically generates detailed meeting briefings, summarizes standup notes using Git commits and CI status, and creates repeatable Bash scripts. It bridges time management and development tasks, ensuring users are always prepared for their next meeting or sprint.

This internal agent skill defines a systematic, multi-step procedure for scanning GitHub repositories to gather comprehensive evidence supporting or explaining bug clusters. The process covers searching open issues, inspecting recent commits, analyzing code paths, and checking deployment history. It assigns evidence confidence tiers (Exact, Strong, Moderate, Weak) to provide a deep, actionable understanding of potential software defects.

This skill guides developers through creating a comprehensive refactoring plan and serving as a Request for Comments (RFC). It orchestrates detailed interviews, codebase analysis, and scope definition. It ensures the refactor is broken down into tiny, safe, incremental commits, culminating in a structured GitHub issue that serves as a definitive architectural and technical decision document.