git-workflow
Git branching strategy and versioning workflow. Use when creating branches, PRs, or releasing versions.
اپنے ایجنٹ کے لیے موزوں صلاحیت تلاش کریں۔
Git branching strategy and versioning workflow. Use when creating branches, PRs, or releasing versions.
Orchestrator AI-specific Git conventions and standards. Branch naming, commit workflow, repository organization. CRITICAL: Follow conventional branch names, use conventional commits, maintain clean git history.
Work on multiple features simultaneously without context switching overhead
Git operations with 100% commit consistency. Handles all git operations for commands including branch creation, atomic commits following project conventions, and PR creation. Always use this skill for git operations to ensure consistency.
Runner group organization strategies for GitHub Actions. Repository access restrictions, workflow controls, and security boundaries for self-hosted runners.
Open状態のGitHub Issueから低品質・曖昧なIssueを検出して分析するスキル。 「Issueが多すぎてどれから対応すべきか分からない」「質問や報告の質を上げたい」場合に使用。 環境変数で指定されたリポジトリのIssueを品質評価し、最もスコアの低いIssueを特定する。
Manage git worktrees with iTerm2 integration. Use when user asks to create isolated development environments, work on features in parallel, manage worktrees, open worktrees in new tabs/windows, switch between worktrees, or close completed worktrees. Triggers on "create worktree", "new worktree", "feature branch with worktree", "open worktree", "switch worktree", "close worktree", "list worktrees", or mentions wanting to work on multiple features simultaneously.
Crear y optimizar workflows de CI/CD multi-repo con GitHub Actions
Generates well-structured git commit messages following conventional commit standards and best practices. Creates clear, descriptive commits with proper type prefixes (feat, fix, docs, refactor, etc.), concise subjects, and detailed bodies when needed. Use when committing code changes, creating git commits, writing commit messages, or when users mention "commit", "git commit", "commit message", "conventional commits", "changelog", or need help structuring version control messages. Ensures commits are atomic, descriptive, and follow team conventions.
Branching strategy guide for Lighthouse LM agentic development. Provides branch selection guidance based on work type (epic/feature/wave), scope, and Progressive Coherence principles. Use when starting new work, implementing epics/features, or deciding branch strategy. Helps agents choose correct branch type and workflow.
Manage TASK_BOARD.md by reading project logs and synchronizing task status. Use when tasks are completed, when progress is made, or when needing to sync task tracking. Reads MIGRATION_LOG.md, DEBUG_LOG.md, GIT_LOG.md to assess actual progress and updates TASK_BOARD.md accordingly. Does NOT modify CLAUDE.md or MIGRATION_LOG.md.
manage GitHub Projects (V2), including board organization, fields, and item tracking
GitHub issue workflow management with gh CLI and native dependency tracking. Use for gh commands, finding next issues, viewing issue dependencies, and claiming issues.
This skill should be used when the user asks to "design a feature", "make architectural decision", "choose a pattern", "select technology", "plan structure", "decide on approach", or requests technical design before implementation. Use for architectural planning, pattern selection, and technical decision-making. Do NOT use for direct code implementation, bug fixes, or simple edits.
Analyzes completed agent sessions to identify what went well, what went wrong, and patterns to improve. Reads from .claude/ folder (session logs, progress.md, git history) and produces actionable insights. Use after completing work sessions to learn from agent behavior and improve future runs.
Process Fireflies meeting transcripts to extract action items, create GitHub issues, compare against existing work, and generate EOS Level 10 Meeting summaries. Use after team meetings or when the user mentions meetings, Fireflies, L10, or action item extraction.