readme-updater
Intelligently update README.md to keep it in sync with code changes. Triggers: readme, 更新 README, update readme, 文檔同步.
Essential command-line tools and system utilities.
Intelligently update README.md to keep it in sync with code changes. Triggers: readme, 更新 README, update readme, 文檔同步.
Codex CLIでレビュー・分析をする。trigger: 「codexにレビューして」「レビューして」「review my changes」
Your approach to handling global committing. Use this skill when working on files where global committing comes into play.
Verify if the current repository uses Jujutsu (jj) instead of git. Use this skill when you or the user needs to confirm the version control system (VCS) state before performing operations.
Analyze git diff to identify code changes requiring documentation updates. Categorizes changes (database/schema, API endpoints, components, configuration, authentication) and suggests relevant documentation files to review. Use when: (1) After making code changes, (2) Before committing significant changes, (3) When adding new features or modifying APIs, (4) During PR preparation, (5) When working with database schemas, API routes, components, or configuration files, (6) To ensure documentation stays synchronized with code changes, (7) For documentation sync and maintenance, or (8) For pre-commit documentation checks. Triggers: check docs, docs check, documentation check, update docs, sync documentation, what docs need updating, check if docs are up to date, after code changes, before committing.
Create well-formatted git commit messages following conventional commits standard. This skill should be used after completing coding tasks to create clear, descriptive commit messages that accurately reflect changes.
This skill should be used when providing context about "modern CLI tools", "best practices for shell configuration", "dotfiles organization", "security patterns for configs", "performance optimization", "git configuration patterns", "modern alternatives to traditional tools", or when the main dotfiles-optimizer skill needs reference knowledge about configuration best practices.
This skill should be used when addressing MISRA-C 2023 or CERT-CPP compliance violations through automated suppression workflows. Use it for analyzing violation reports, applying systematic suppressions, and managing the git-based compliance workflow from initial analysis to pull request creation.
Generate comprehensive changelogs from git history following Keep a Changelog format. Use when creating release notes or maintaining version history.
This skill should be used for detailed guidance on Jujutsu (jj) VCS operations, including committing, pushing, searching history, and working with revisions/revsets. Use it when the user asks "how do I use jj?", "translate git to jj", ask to interact with VCS using jj or for specific jj command syntax.
Write production-ready Go backends, CLIs, and APIs following modern best practices from top tier tech companies. Use this skill when creating or reviewing Go code for (1) backend services and APIs, (2) command-line tools, (3) code requiring proper error handling, concurrency, or testing patterns, (4) any Go development requiring adherence to established style guidelines. Includes comprehensive linting configuration and detailed style guide.
Auto-check and update key documentation before Git commits to keep docs in sync with code. LOAD THIS SKILL WHEN: Before git commit/push | User says "準備提交", "sync docs", "發布", "release" | code changes affect documentation. CAPABILITIES: Update README, CHANGELOG, ROADMAP, ARCHITECTURE, Memory Bank; minimal changes; semantic versioning; Keep a Changelog format.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
Remove AI-generated code slop from current branch. Identifies and removes inconsistent comments, over-defensive code patterns, and style mismatches introduced by AI. Use when: cleaning up AI-generated code, before committing AI changes, after code generation session.
Guide documentation updates through the Architecture Decision Workflow. You must use this skill when: (1) Code changes reveal undocumented or conflicting conventions, (2) A learning or incident suggests documentation should change, (3) Reviewing changes for durable context updates, (4) Asked to update documentation, (5) PR introduces patterns that may need documenting, (6) You plan on adding or changing a file in the docs/ directory or any CLAUDE.md files. Ensures all documentation changes are intentional, traceable, and human-auditable.
Create thoughtful git commits with conventional commits format. Invoke when user says "commit", "commit these changes", "create a commit", "save my changes", or after completing a task.
Create well-structured git commits. Use when committing code changes.
Use this agent when understanding the historical context and evolution of code changes, tracing the origins of specific code patterns, identifying key contributors and their expertise areas, or analyzing patterns in commit history. Triggers on requests like "git history analysis", "why was this written", "who owns this code".
Review code for quality, security, and best practices. Use for PR reviews, code quality checks, security audits, and pre-merge reviews.
Generates conventional commits based on file changes. Analyzes diffs and creates properly formatted commit messages.
Create git commit messages based on current staged changes. Has support for git emoji messages.
Systematic code review workflow to evaluate changes against Java and Spring standards. Use when reviewing Pull Requests, commits, or diffs. Ensures robustness, maintainability, and adherence to best practices.
Systematic workflow for addressing PR review comments. Use when the user wants to work through PR review comments (from Copilot, teammates, or other reviewers). Triggers include phrases like "work through PR comments", "address review feedback", "go through the review on PR