kano-commit-convention-skill
Commit convention linting and changelog automation following the Kano commit format.
Essential command-line tools and system utilities.
Commit convention linting and changelog automation following the Kano commit format.
Generate beautiful CHANGELOG.md from git commits following Keep a Changelog format
Generate nested AGENTS.md coding guidelines per module (monorepo-aware), detect languages/tooling, ask architecture preferences, and set up missing formatters/linters (Spotless for JVM).
This skill should be used when the user needs to review and respond to GitHub Pull Request comments. It automatically fetches review comments (both inline code comments and PR-level comments) from GitHub Codex, Claude Code, or human reviewers, organizes them by priority, and lets the user select which items to address using AskUserQuestion. After the user selects items, the main agent automatically implements the fixes.
Setup and manage git hooks for pre-commit, pre-push automation (lint, test, format)
Extract and track builder commitments from critique exegesis. Use /commitments to audit promises made in prose, verify implementation status, and identify unfulfilled obligations.
MANDATORY setup for all projects. Automated code quality enforcement before commits. Prevents bad code from entering repository.
Intelligently detects when too many files are staged and automatically groups them by feature or functionality using Conventional Commits with user language preference
Strict detection and removal of unrelated files before PR creation
Guide for creating and maintaining repository-local CLAUDE.md files that capture project-specific context, patterns, and conventions. Use when initializing repositories for Claude Code, updating project memory, or understanding effective repository memory structure.
Generate user-friendly changelogs from git commits for releases
Queries indexed repositories via Greptile API for codebase-aware answers. Use when asking natural language questions about code architecture, searching for implementations, understanding how features work, or locating specific code patterns across the repository.
Use when completing tasks, implementing major features, or before merging to verify Flutter code meets requirements
Systematic codebase exploration using tree-sitter AST analysis and repomix semantic search. Use when: (1) User asks to explore/analyze/find/search codebase, (2) Looking for functions/classes/symbols/patterns, (3) Understanding project structure, (4) Tracing dependencies/usage, (5) ANY code analysis task. CRITICAL: NEVER use basic filesystem tools (find, grep, Glob, Read multiple files) when tree-sitter MCP or repomix tools are available.
Provides documentation standards for README, API docs, code comments, changelogs, and project cleanup. Use when writing documentation, README files, API references, or cleaning up project files.
Best practices for project documentation including README, CONTRIBUTING, CHANGELOG, and Markdown files. Use when updating documentation, writing README sections, or maintaining project docs.
Performs comprehensive code review on git diffs and generates review.md with quality scores, critical issues, performance concerns, and potential bugs. Use when user requests to review changes, check code quality, analyze diffs, or validate LLM-generated code
Intelligently update README.md to sync with code changes. Triggers: readme, 說明, 更新說明, update readme, 文檔同步.