kano-commit-convention-skill
Commit convention linting and changelog automation following the Kano commit format.
Discover business git workflows skills, compare source repositories and read the instructions for each workflow.
Commit convention linting and changelog automation following the Kano commit format.
Commit convention linting and changelog automation following the Kano commit format.
Commit convention linting and changelog automation following the Kano commit format.
Commit convention linting and changelog automation following the Kano commit format.
Guidelines for creating high-quality Freenet pull requests. This skill should be used when creating PRs for freenet-core, freenet-stdlib, or related repositories. Emphasizes quality over speed, thorough testing...
Pull issues, metrics, quality gates, and analysis data from SonarCloud. Use when checking code quality, security vulnerabilities, test coverage, technical debt, or CI/CD quality gates.
规范化的代码提交工具,自动生成符合 Conventional Commits 格式的提交信息,并支持用户确认机制
Guide for writing conventional commits with gitmoji
Use this skill when posting the final summary comment after all inline comments are posted. Apply as the LAST step of code review after all findings are classified and inline comments are complete. Detects cont...
Analyzes git commits and changes within a timeframe or commit range, providing structured summaries for code review, retrospectives, work logs, or session documentation.
Performs comprehensive analysis of Claude Code sessions, examining git history, conversation logs, code changes, and gathering user feedback to generate actionable retrospective reports with insights for contin...
Use this skill when re-reviewing a PR that already has comments or when responding to developer changes after initial review. Apply when PR threads exist or when reviewing force-pushed commits. Handles incremen...
Use this skill when posting inline comments to GitHub pull requests. Apply when formatting comments following Bitwarden engineering standards with severity emojis, clear explanations, and actionable suggestions...
Use when cleaning up Git history, applying commits across branches, finding bug introductions, or recovering from mistakes. Covers rebase, cherry-pick, bisect, worktrees, and reflog.
Use `a gh check-pr-review` to fetch and address PR review comments. Use this skill when checking PR review feedback, viewing unresolved threads, or addressing reviewer comments.
Use this skill when committing changes. This skill enforces writing meaningful commit messages with both Why and What sections, and provides Git workflow guidelines.
Use `a gh issue-agent` to view and edit GitHub Issues. Use this skill when working with GitHub Issues - viewing issue content, editing issue body/title/labels, or adding/editing comments.
Use this skill when creating a Pull Request. This skill provides the workflow for drafting, reviewing, and submitting PRs using a ai pr-draft command.
Guidance for using the flo CLI to manage git worktrees from GitHub issues. Use when starting work on issues, cleaning up finished work, or managing multiple parallel workstreams.
Use when adding allow/deny rules to Claude Code, granting project permissions, troubleshooting "permission denied" errors, "skill requires approval" prompts, or setting up shared team permissions. Also use when...
Use when user says "sync" or wants to commit, push, pull, and run the dotfiles sync script. Also use when creating migrations for one-time cleanup on existing machines, or when a migration fails.
Safely sync a branch with origin/main using fetch + rebase, with an optional "accept current" conflict policy.
Systematic GitHub issue creation from requirements. Analyzes codebase, breaks down requirements into multiple issues with dependencies, proposes detailed issues for review, and creates them after user approval....
Autonomous issue management - fetches open GitHub issues, analyzes priorities, detects dependencies, spawns parallel subagents, and verifies results. Triggers: /run-issues, autonomous issues, batch issues, para...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.