CI/CD integration - GitHub Actions, automation, pipeline integration
Skills(SKILL.md)は、AIエージェント(Claude Code、Cursor、Codexなど)に特定の能力を追加するための設定ファイルです。
詳しく見る →CI/CD integration - GitHub Actions, automation, pipeline integration
GitHub Actions CI/CD patterns for automated testing, building, and deployment. Covers workflow syntax, secrets management, matrix builds, and deployment strategies.
Comprehensive CI/CD pipeline patterns skill covering GitHub Actions, workflows, automation, testing, deployment strategies, and release management for modern software delivery
CI/CD and operations practices including GitHub Actions, Kubernetes, and operational tooling. Use when working with deployment and infrastructure.
Pre-push validation checklist (cargo fmt, clippy with zero warnings, feature flag testing, test suite), CI monitoring, merge process, and release quality gates. Use when preparing to push code, validating changes before PR, running CI checks, merging PRs, or preparing releases.
Guide for GitHub Actions workflows, test orchestration, parallel testing,
Diagnoses and fixes CI/CD pipeline failures. Use when user mentions CI failures, build errors, test failures, or pipeline issues. Do NOT load for: local builds, standard implementation work, reviews, or setup.
Debug GitHub Actions workflow failures, CI build issues, test failures in CI, and deployment problems. Use when workflows fail, artifacts aren't uploaded, or CI-specific errors occur.
This skill should be used when analyzing failed GitHub Actions CI/CD runs for Breenix kernel development. Use for diagnosing test failures, parsing QEMU logs, identifying kernel panics or faults, understanding timeout issues, and determining root causes of CI failures.
Analyze GitHub Actions CI failures for the current branch. Use when the user asks about CI status, test failures, build errors, GitHub Actions problems, or mentions checking CI, workflow failures, or pipeline status.
Diagnose CI failures and stabilize pipelines. Use when a mid-level developer needs to resolve flaky or failing builds.
Fix GitHub Actions CI failures using GitHub CLI (gh): inspect runs/logs, identify root cause, patch workflows/code, rerun jobs, and summarize verification. Use when GitHub Actions CI is failing or needs diagnosis.
Automated CI/CD pipeline fixer - watches CI, fixes errors locally, commits, and loops until green. Use when CI is failing and you want to automatically fix and verify changes.
>
CI Job 失败分析知识库,包含失败类型分类、置信度评估、技术栈识别和常见错误模式
Use after creating PR - monitor CI pipeline, resolve failures, address review feedback, and merge when all gates pass
Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable
Manage CI pipelines with error handling, recovery, and complex dependencies. Use when testing pipeline workflows. Not for simple linear scripts or unit testing individual tasks.
Set up CI/CD pipelines with GitHub Actions. Use when creating new projects, adding automation, or when manual verification becomes bottleneck. Covers lint, test, build, deploy automation.
Configure CI/CD pipelines for GitHub Actions, GitLab CI, CircleCI with best practices
Use when setting up CI/CD pipelines. Teaches pipeline design principles and references platform-specific templates.
Run and interpret pnpm lint, pnpm typecheck, pnpm build, and pnpm format in a Turborepo monorepo; diagnose CI-style failures; propose minimal diffs; and deliver a fix plan, files touched, and validation commands checklist. Use when verifying CI readiness or fixing lint/typecheck/build/format failures in Turborepo repositories.
Comprehensive CI/CD and automation audit skill. Catalogs all pipelines, assesses operational health, identifies gaps, and provides prioritized recommendations for optimization. Includes error cataloging and root cause analysis framework.
Use when optimizing GitLab CI/CD pipelines for performance, reliability, or maintainability. Covers pipeline optimization and organizational patterns.
**Persona: Senior Platform Engineer - CI/CD Specialist**
Loop 3 of the Three-Loop Integrated Development System. CI/CD automation with intelligent failure recovery, root cause analysis, and comprehensive quality validation. Receives implementation from Loop 2, feeds failure patterns back to Loop 1. Achieves 100% test success through automated repair and theater validation. v2.0.0 with explicit agent SOPs.
cicd-master
Use when setting up CI/CD pipelines, experiencing deployment failures, slow feedback loops, or production incidents after deployment - provides deployment strategies, test gates, rollback mechanisms, and environment promotion patterns to prevent downtime and enable safe continuous delivery
cicd-pipeline-generator
GitHub Actions, GitLab CI, Jenkins, and automated deployment pipelines
Create and configure CI/CD pipelines with security-first best practices. Triggers on requests to set up CI/CD, add GitHub Actions, create pipelines, automate testing/deployment, configure workflows, add continuous integration, or automate releases.
Expert in Cilium eBPF-based networking and security for Kubernetes. Use for CNI setup, network policies (L3/L4/L7), service mesh, Hubble observability, zero-trust security, and cluster-wide network troubleshooting. Specializes in high-performance, secure cluster networking.
Expert guidance for designing, implementing, and testing zero-knowledge proof circuits using circom.
circuit-debugger
You are an expert in circular economy design and implementation for supply chains. Your goal is to help organizations transition from linear "take-make-dispose" models to circular systems that elimina
CISO & Product Manager skill providing security-focused product vision, risk assessment, and strategic guidance for caro development
Build trading systems in the style of Citadel Securities, the world's largest market maker. Emphasizes ultra-low latency, deterministic execution, kernel bypass networking, and high-frequency trading infrastructure. Use when building latency-critical systems, market making engines, or high-performance trading platforms.
Format citations and bibliographies in multiple academic styles (APA, IEEE, Chicago, Harvard, MLA, Nature, Science). Use when: (1) Converting between citation styles for different journals, (2) Cleaning and standardizing bibliography entries, (3) Validating citation formatting before submission, (4) Generating properly formatted reference lists, (5) Checking citation consistency across manuscripts.
Comprehensive Citrix Provisioning Services (PVS) expertise for infrastructure management, troubleshooting, and optimization. Use when working with PVS environments including vDisk management, target device provisioning, boot process troubleshooting, write cache configuration, version management, replication, performance optimization, or any PVS-specific administration tasks.
Systematic Citrix issue diagnosis and resolution. Use when troubleshooting VDA registration failures, session launch problems, application errors, performance issues, or connectivity problems. Provides structured troubleshooting workflows, log analysis techniques, and proven solutions for common Citrix issues.
マクロ設計のベストプラクティスを適用。マクロ作成・レビュー時に使用
malletリンターのルールと設定を適用。コードレビュー・品質チェック時に使用
Autonomous claims drafting and optimization agent. Drafts, analyzes, and refines patent claims to maximize protection while ensuring validity.
Validate documentation for unsupported claims, made-up metrics, and unverifiable statements. Use when relevant to the task.
Process expense claims by matching YNAB transactions with uploaded receipts. Use when the user mentions claims, expenses, reimbursements, receipts, or YNAB TODOs.
Generate Clap-based Rust CLI applications with derive macros, subcommands, and modern Rust patterns. Creates production-ready Rust CLI with proper cargo structure.
Clarify ambiguous requests by researching first, then asking only judgment calls; stop before implementation.
Intensive requirement clarification using structured AskUserQuestion workflow. Gathers MUST_HAVE (blocking) and NICE_TO_HAVE (optional) information before implementation. Use when: (1) starting new feature implementation, (2) requirements are ambiguous, (3) multiple approaches possible, (4) before writing any code. Triggers: /clarify, 'clarify requirements', 'ask questions', 'gather requirements'.
clarify-spec
Python class design conventions for this codebase. Apply when writing or reviewing classes including interfaces, inheritance, composition, and attribute access.