global-committing
Your approach to handling global committing. Use this skill when working on files where global committing comes into play.
Script and automate repetitive tasks and workflows.
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 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.
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.
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.
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
코드 리뷰 스킬. Git 변경사항, PR, 특정 파일을 분석하여 품질/보안/성능 관점에서 리뷰를 제공합니다. 사용 시기: (1) /review - 현재 staged/unstaged 변경사항 리뷰 (2) /review <file> - 특정 파일 리뷰 (3) /review-pr <number> - GitHub PR 리뷰 (4) 코드 품질 검토 요청 시 (5) 보안 취약점 검토 요청 시 (project)
Generates properly formatted commit messages following project conventions. Use when creating commits or when users need help writing commit messages. Inspects staged changes and creates messages with component tags, concise summaries, and detailed descriptions.
Project structure, conventions, and key patterns for this codebase
Analyzes git changes and creates well-structured, atomic commits following project conventions. Detects commit style, plans optimal commit grouping, and ensures proper separation of concerns.
Generate a comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes.. Use when Creating App Store “What’s New” text from git history..
Analyze the Ark codebase by cloning the repository to a temporary location. Use this skill when the user asks questions about how Ark works, wants to understand Ark's implementation, or needs to examine Ark source code.
Perform an expert frontend code review directly from a GitHub Pull Request using gh CLI.