Skill UI

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.

A powerful tool that converts complex Unified Modeling Language (UML) diagrams—such as Sequence, Class, Activity, and State diagrams—into plain text ASCII art. This is crucial for documentation in environments that do not support image embedding, such as terminal sessions, README files, or Git commit messages. Supports both standard ASCII and enhanced Unicode ASCII formats for better visual fidelity.

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.

This skill provides templates and guidelines for conducting code reviews in Chinese-speaking teams. It helps balance feedback tone, avoiding being too polite or too blunt. It includes priority labeling (must fix, suggest, reference), mixed Chinese-English comment standards, and commit message formats. It also addresses common anti-patterns like excessive politeness or style wars, ensuring code quality without damaging team morale.

Analyzes git diffs to generate narrative commit messages explaining the why behind changes, following Conventional Commits format. Helps developers write clear, meaningful commit logs for version control and pull requests by transforming raw code changes into structured stories.

This skill generates structured and standardized Git commit messages following the Conventional Commits specification. By analyzing code changes (via diff or status), it helps developers automatically create clear, actionable, and searchable commit history messages, ensuring consistency across the project.

This skill automatically rewrites raw commit messages to adhere to professional engineering standards. It strips out common 'AI/marketing slop' phrases (like 'robust implementation' or 'leverage') while strictly maintaining the Conventional Commits format. It ensures subjects are concise, bodies provide necessary context (why, breaking changes), and the tone is direct and actionable, making your project history clean and readable.

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.

This skill reconstructs the full narrative behind a piece of code by analyzing local Git history. Instead of just naming the last author (like git blame), it traces the file's origin, tracks subsequent changes, identifies related companion files, and extracts intent clues from commit messages. Use this when you need to know *why* code exists before refactoring, making risky edits, or understanding complex system behavior.

This skill generates standardized commit messages adhering to the popular gitmoji convention. By analyzing a git diff, staged files, or a plain description of changes, it selects the single most appropriate emoji to categorize the intent (e.g., feature, bug fix, refactor). It outputs a concise, well-formed, and highly scannable commit message for the user to copy, without running any actual git commands.

This utility guides users in creating standardized and descriptive commit messages for staged changes using the Conventional Commits specification. It enforces structure, defining types (feat, fix, chore, etc.), scopes, and detailed body/footer requirements, ensuring a clear and maintainable project history.

Automate changelog generation from commits, PRs, and releases following industry standards like Keep a Changelog. This skill helps set up release workflows, generate release notes, and standardize commit message formats. It supports conventional commits and semantic versioning management. Use it for CI/CD pipelines and version control processes to ensure consistent documentation and maintain project history.