git-workflow
Especialista em Git, estratégias de branching, resolução de conflitos e workflows colaborativos
Especialista em Git, estratégias de branching, resolução de conflitos e workflows colaborativos
배포 상태 실시간 모니터링 및 Health Check. GitHub Actions 워크플로우 진행 상황, K8s Pod 상태, Health Check 결과 확인. "배포 상태", "배포 확인", "정상 동작" 요청 시 사용.
Complete ACM (Automated Condition Monitoring) expertise system for predictive maintenance and equipment health monitoring. PROACTIVELY activate for: (1) ANY ACM pipeline task (batch runs, coldstart, forecasting), (2) SQL Server data management (historian tables, ACM output tables), (3) Observability stack (Loki logs, Tempo traces, Prometheus metrics, Pyroscope profiling), (4) Grafana dashboard development, (5) Detector tuning and fusion configuration, (6) Model lifecycle management, (7) Debugging pipeline issues. Provides: T-SQL patterns for ACM tables, batch runner usage, detector behavior, RUL forecasting, episode diagnostics, and production-ready pipeline patterns. Ensures professional-grade industrial monitoring following ACM v11.0.0 architecture.
gh CLIでGitHub Issueを作成するスキル。現在の動作/期待する動作/再現手順/環境情報などの最小入力から、AIが作業可能な構造化Issue(調査・修正・検証の手順と受け入れ条件付き)を作成する。Codex/Claude/Gemini/Cursorで共通化したIssue作成を行うときに使用する。
GitHub Actions 워크플로우 로그를 조회하고 분석합니다. "CI 로그 확인해줘", "워크플로우 실패 원인 분석해줘", "GitHub Actions 상태 알려줘", "빌드 로그 보여줘", "테스트 실패 로그 확인" 등을 요청할 때 활성화됩니다.
Check GitHub Project board status for the monorepo. Use when user asks about board status, what's in progress, sprint status, or issue tracking.
Coordinates multi-component releases, feature flags, versioning, and rollback strategies. Trigger terms: release management, release planning, release coordination, feature flags, canary deployment, progressive rollout, release notes, rollback strategy, release train, deployment coordination, versioning, changelog, release approval, deployment checklist. Manages complex release workflows: - Multi-component release coordination - Feature flag strategy and management - Versioning and changelog generation - Canary and blue-green deployments - Progressive rollout strategies - Rollback procedures - Release approval workflows - Post-release verification Use when: planning releases, coordinating multi-service deployments, managing feature flags, or generating release notes.
Prime context for a task - research, scan codebase, gather domain constraints. Use when starting implementation of a task file, PRD, or clear task description.
Follow truth-first development with focused feature work, accurate spec maintenance, clean version control, environment-based configuration, and infrastructure-as-code deployments. Use this skill when managing requirements, working in branches, handling configuration, reviewing code, maintaining documentation, or deploying with Ansible. Applies to all development activities requiring honest communication, systematic processes, dependency management, and radical transparency in documentation and decision logs.
Create a delivery roadmap that translates strategy into sequenced releases with milestones and dependencies.
Orchestrates Atlas workflow tier selection for software development tasks
Use when assessing team resilience, planning for developer departures, calculating bus/truck factor, identifying knowledge silos, or evaluating organizational risk - maps code ownership from git history and identifies single points of failure using research-backed thresholds (>80% ownership = silo)
Practice radical candor by delivering only verified, tested code with data-backed decisions, immediate problem flagging, and honest status communication. Use this skill when making claims about code behavior, reporting system status, identifying risks, documenting missing coverage, or challenging assumptions. Applies to all development activities requiring factual accuracy, evidence-based assertions, gap ownership, and closing the loop on delivered work through validation and independent review.
Creates GitHub issue with task checklist based on architecture documents (specs.md, frontend.md, backend.md). Run after reviewing the planning documents.
Tracks and monitors GitLab merge request activity including comments, status, and real-time updates
skill that dictates the deployment strategy for local development
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.
Loads project context, lists existing specs and changes, searches capabilities and requirements. Use when user asks about project state, existing specs, active changes, available capabilities, or needs context discovery. Triggers include "what specs exist", "show changes", "list capabilities", "project context", "find specs", "what's in the spec", "show me specs".
Comprehensive DevOps and deployment workflow that orchestrates infrastructure automation, CI/CD pipelines, container orchestration, and cloud deployment. Handles everything from infrastructure as code and pipeline setup to monitoring, scaling, and disaster recovery.
Use after planning or implementing non-trivial tasks - runs Codex MCP background verification/review for quality gates (plan validation + implementation review)
Understand Conventional Commits, GitHub issue management, and Pull Request workflows. Apply best practices for collaborative development.