Loading...
Loading...
Found 10 Skills
Pre-commit hook standards and configuration. Use when configuring pre-commit hooks in repositories, checking hook compliance, or when the user mentions pre-commit, conventional commits, or hook configuration.
All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly.
A comprehensive Git agent skill combining strategic workflows, strict conventional commit standards, and safe execution protocols. Acts as a senior engineer to guide users through atomic, verifiable, and standardized git operations.
Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.
A comprehensive Git agent skill combining strategic workflows, strict conventional commit standards, and safe execution protocols. Acts as a senior engineer to guide users through atomic, verifiable, and standardized git operations.
Commit standards for Engram contributors. Trigger: Any commit creation, review, or branch cleanup.
Generate Conventional Commits messages. Use when: creating commits, writing commit messages, committing changes. Triggers: /git-commit, commit this, commit my changes, finishing code changes.
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
Generate Chinese Git commit messages that comply with the Conventional Commits specification. Use this when users request to create Git commits, generate commit messages, or mention "submit code", "git commit", or "Chinese commit". Automatically analyze code changes to generate standardized Chinese commit messages with correct type prefixes (feat/fix/docs, etc.) and clear descriptions.
Create Git commit messages that conform to Conventional Commits 1.0.0, including type/scope/description format, optional body, trailer-style footers, and explicit BREAKING CHANGE signaling. Use when users ask to draft commit messages, commit current changes, rewrite a commit message into conventional format, or enforce conventional commit standards in a repo.