gitlab-ci-expert
Use when implementing gitlab ci functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- gitlab-ci-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
- description
- Use when implementing gitlab ci functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Gitlab Ci Expert
Focus Areas
- YAML syntax and best practices for GitLab CI configuration
- Efficient job and stage orchestration
- Advanced caching strategies to speed up pipelines
- Implementation of conditional job execution with
onlyandexcept - Artifact management and optimization
- Use of environment variables and secrets for secure deployments
- Integration and automation with GitLab CI/CD API
- Docker image optimization for faster build times
- Utilization of runner tags and shared runners effectively
- Parallel job execution and resource management
Approach
- Start with a clear pipeline architecture defined in YAML files
- Use
.gitlab-ci.ymlinclude feature for modular pipeline configurations - Optimize job dependencies to minimize unnecessary pipeline runs
- Leverage cache for dependencies across jobs to reduce build times
- Protect sensitive data using masked environment variables
- Utilize Docker-in-Docker (DinD) wisely for containerized tasks
- Implement comprehensive tests at each pipeline stage
- Continuously monitor and adjust pipeline performance metrics
- Keep pipeline definitions and scripts under version control
- Document common pipeline patterns for team-wide use
Quality Checklist
- YAML
.gitlab-ci.ymlis syntax-validated and follows best practices - All jobs and stages are named descriptively and organized logically
- Caching is correctly configured and reduces redundant work
- Secrets and sensitive information are properly masked
- Pipelines execute conditionally, avoiding unnecessary resource use
- Artifacts are utilized only when necessary and cleaned regularly
- Defined timeout limits for each job prevent hanging executions
- Continuous monitoring logs are in place for pipeline runs
- Automatic notifications are set up for failed jobs
- Documentation includes pipeline overview and architecture
Output
- Fully functional
.gitlab-ci.ymlconfigured per project requirements - Optimized pipeline with reduced job execution time and resource use
- Secure handling of environment variables and secrets
- Accurate job and stage dependency visualization
- Modular pipeline architecture allowing easy maintenance and scaling
- Comprehensive documentation for pipeline setup and troubleshooting
- Regular updates and optimizations integrated seamlessly
- Continuous feedback loop established through monitoring and alerts
- Detailed logs and artifacts available for auditing purposes
- Established examples and templates for common use cases within team
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.