handler-source-control-gitlab
GitLab source control handler centralizing Git CLI and GitLab API operations with protected branch safety
Script and automate repetitive tasks and workflows.
GitLab source control handler centralizing Git CLI and GitLab API operations with protected branch safety
Create and manage Git worktrees for parallel development workflows
Safe git operations including commits, branches, merges, worktrees, and conflict resolution. Use when user wants to commit and push changes, manage branches, resolve conflicts, or create isolated workspaces. Activates when user says "commit", "push", "merge", "branch", "pull", "rebase", "worktree", "conflict", or similar git workflow requests.
Advanced git workflows including rebase, worktrees, bisect, hooks, and monorepo patterns
Capable of performing comprehensive code reviews on git commits. Analyzes commit changes, investigates side effects in the codebase, and categorizes findings by severity levels (critical, major, minor, nit).
Scans project dependencies for known vulnerabilities, outdated packages, and license compliance issues. Trigger keywords: dependency, vulnerability, CVE, npm audit, outdated, license, supply chain, SBOM.
Git commit best practices with conventional commits format and atomic commit principles. Use when committing code to ensure clear, meaningful commit history with proper type prefixes and semantic versioning support.
Generates comprehensive, professionally-formatted changelogs for SDL3 HammerEngine from git history. Analyzes code changes, runs tests, includes architect review, and produces detailed documentation following World Update format. Use when documenting updates, preparing releases, or creating detailed change reports.
This skill should be used when the user asks to "write a commit message", "format commit", "commit message style", or needs guidance on conventional commit format.
Clone and explore external codebases using the better-context CLI. Use this skill when: - User wants to explore a GitHub repository (e.g., "explore anthropics/claude-code") - User asks how a library/framework works and you need to read its source - User wants to understand implementation details of an external project - User provides a repo URL or owner/repo and wants you to examine it
既存GitHubリポジトリのメンテナンス(リリース、変更履歴、Issue等)。ghコマンド使用。 トリガー例: 「リリースノート」「リリース」「issue」「repo-maintain」 ※ PR 作成・マージは repo-flow スキルを使用
Generates git patch files from codebase modifications for local application. Use when user mentions patch, diff, export changes, bring changes back, apply locally, or after editing uploaded codebases.
GitHub source control handler centralizing Git CLI and GitHub API operations with protected branch safety
GitHub-specific sync mechanism - file copying, pattern matching, and safety checks
Run focused `kit` CLI commands (file-tree, symbols, search, semantic discovery, dependency analysis, and exports) to build high-signal repository context fast. Use when you need to understand an unfamiliar codebase, prep context for Claude, plan refactors, audit dependencies, or answer “where is X implemented?” without manually grepping.
Generate commit messages following the DAFT convention, which requires exactly one letter as the commit message. Use this skill when creating commits, suggesting commit messages, or validating commit message format.
Apply Progressive Disclosure principles to organize large documentation projects. Restructure docs into hierarchical structure, reduce token usage by 95%+, and create README files for navigation.
Git version control operations including status, branches, commits, diffs, and worktree management. Use when working with git repositories, reviewing changes, or managing branches.
Working with .autodoc/ directory, automatic documentation generation, semantic doc search
Review code diffs for bugs, edge cases, state issues, and consequences. Provide prioritized findings with specific fixes.
Detects when high-level project documentation is stale based on code/config changes and generates update suggestions
Security fix patterns for configuration and deployment vulnerabilities (path traversal, debug mode, security headers). Provides language-specific secure implementations.
Quick routine security checks for secrets, dependencies, and common vulnerabilities. Run frequently during development. Triggers: security scan, quick scan, secrets check, vulnerability check, security check, pre-commit security, routine security.