Script and automate repetitive tasks and workflows.
Route ALL git operations to appropriate resources. Load reference files before responding. Scope: status, diff, log, commits, branches, conflicts, rebasing, code review. Triggers: "git", "status", "diff", "log", "commit", "branch", "merge", "conflict", "rebase", "stash", "cherry-pick".
Format git commit messages following Conventional Commits 1.0.0 specification. Use when the user asks to commit changes, create a git commit, or mentions committing code. Ensures consistent, semantic commit messages that support automated changelog generation and semantic versioning.
Use this skill when working with dotfiles managed by yadm. This includes pulling remote changes, committing and pushing dotfile changes, modifying configuration files (shell, editor, terminal, git, etc.), viewing tracked files, resolving merge conflicts, and maintaining the dotfiles repository.
Analyze git repositories and generate comprehensive markdown documentation for quick understanding. Use when user asks to "analyze this repo", "document the codebase", "explain how this project works", "generate repo docs", "understand this codebase", or wants documentation about project architecture and modules. Triggers on requests for codebase analysis, architecture documentation, module documentation, or project understanding.
codereview / code review / 代码审查 - Go 代码深度审查技能，专注于性能、安全性、并发安全和可读性。支持审查本地未提交代码、最近 commit 或指定的 commit/分支/tag。支持简洁/详细两种输出模式。
Find real-world code examples across millions of GitHub repositories. Use when the user wants to see how others implement something, find usage patterns, or discover code examples in the wild.
Code review guidelines covering code quality, security, and best practices.
Use when reviewing code changes, auditing documentation accuracy, validating technical claims before merge, or user says "verify claims", "factcheck", "audit documentation", "validate comments", "are these claims accurate".
Validate changes for factual accuracy, completeness, and intent preservation without modifications. Scope: fact-checking, verifying refactors, validating imports, checking rewrites, comparing versions, reviewing documentation changes. Triggers: "fact-check", "verify", "validate", "compare versions".
Review and improve documentation quality using best practices. Use when reviewing changelogs, documentation, or any written content to ensure clarity, accuracy, and helpfulness.
Validate documentation files for completeness, accuracy, and consistency with the codebase. Use when user mentions "check documentation", "validate docs", "is the README up to date?", requests documentation review, says "docs are wrong" or "fix the docs", or is working on documentation improvements. Covers README files, API docs, CHANGELOG, and any markdown documentation.
Apply consistent documentation standards and style guidelines when creating, reviewing, or improving project documentation (README, architecture docs, guides, references). This skill should be used when writing new documentation, reviewing existing docs for style consistency, or when users request documentation improvements or style guide compliance checks.
Comprehensive code quality review focusing on DRY (Don't Repeat Yourself), KISS (Keep It Simple, Stupid), and Clean Code (Easy to Read) principles. Use when reviewing code changes, analyzing code quality, or assessing code maintainability for any feature, bug fix, or refactoring task.
Extracts naming conventions, code style guidelines, and structural patterns specific to the project. Analyzes variable naming, function signatures, file organization, and comment styles.
Review code changes (diffs, PRs, patches) and provide structured, actionable feedback on correctness, maintainability, and test coverage. Use when the user asks for a code review, requests feedback on a patch/PR, or wants an assessment of changes.
Validates PopKit code quality using concrete metrics for DRY, coupling, cohesion, and architectural patterns
This skill should be used when CodeRabbit code review feedback needs to be processed and fixed systematically. Use after running `coderabbit --plain` to automatically save feedback, analyze issues using MCP tools, and implement minimal code fixes with proper planning.
Automatic OWASP security checks on generated code. Use when: any code is generated in the pipeline. Triggers: internal use only.
Runs Static Application Security Testing (SAST) using Semgrep. Scans source code for vulnerabilities, security anti-patterns, and OWASP Top 10 issues. Use when user asks to "run SAST", "scan for vulnerabilities", "static analysis", "code security scan", "静的解析", "脆弱性スキャン".
FTC skill code quality and structure checks. Activates when reviewing PRs, validating skills, or checking plugin compliance with marketplace standards. Use when reviewing pull requests, running local code review, or validating skill structure before submission.
Review static site code for bugs, security issues, performance problems, accessibility gaps, and CLAUDE.md compliance. Enforces pure HTML/CSS/JS standards, minimal page weight, mobile-first design. Use when completing features, before commits, or reviewing changes.
Guides systematic code refactoring to improve code quality, maintainability, and design. Identifies code smells, applies refactoring patterns, ensures test coverage, and follows safe refactoring practices. Produces cleaner, more maintainable code while preserving functionality. Use when improving code quality, eliminating technical debt, preparing for feature additions, addressing code smells, or when users mention refactoring, code cleanup, improving design, reducing complexity, or modernizing legacy code.
