Results for “gitlab”

Build a GitLab CI/CD pipeline with automated checks for vulnerable code, dependencies, container images, running applications, and exposed secrets. Covers scanner configuration, consolidated findings, and approval policies for serious vulnerabilities before production deployment.

• Add automated security scans to .gitlab-ci.yml
• Check dependencies and container images for known vulnerabilities
• Detect credentials and API keys committed to source control

Build GitLab workflows that automate building, testing, and deployment. The skill covers pipeline stages, dependency caching, runners that execute jobs, and manual approval before production deployment, with examples for Docker, Kubernetes, and Terraform.

• Automating builds and tests in GitLab
• Reviewing caches to improve pipeline performance
• Separating staging and production deployments

Review a GitLab merge request linked to a Factory work item, verify the current commit, and publish findings with a test report. It records the review verdict on the card and prepares a session handoff without merging.

• Review a GitLab merge request assigned through Factory
• Verify earlier review findings against the current commit
• Publish test results and an evidence-based verdict

Re-review a GitLab merge request after new commits, track the outcome of every previous finding, and inspect both new changes and the full proposal. Verify the current code, then publish a test report and review verdict.

• Re-reviewing a merge request after fixes
• Tracking the resolution of earlier review findings
• Checking new commits for regressions and incomplete fixes

Inspect project files to identify languages and build tools, then generate starter GitHub Actions or GitLab CI workflows. Set up automated checks, caching, and deployment stages that reflect the project’s commands and target environments.

• Setting up automated checks for a new project
• Reworking fragile pipeline configuration
• Moving between GitHub Actions and GitLab CI

Inspect proposed changes in GitHub, GitLab, or Perforce for review feedback, failed automated checks, and incomplete descriptions. It separates actionable findings from informational or resolved comments, then helps fix issues and close addressed review threads when requested.

• Inspect a change before submission
• Identify failed checks and required fixes
• Organize human and bot review feedback

Set up Strix security checks in CI/CD to test pull request changes, report verified vulnerabilities, and gate merges. Covers both a CLI running on your own infrastructure and a managed service with pull request comments.

• Check pull request changes for vulnerabilities before merging
• Add Strix scans to GitHub Actions or GitLab CI
• Choose between managed reviews and scans on your own runners

Review code changes on GitHub or GitLab and investigate failed CI checks, the automated checks run on code. Use logs to guide fixes, push commits, and share review comments and repair summaries.

• Review code changes and leave inline comments
• Investigate failed CI checks and fix the code
• Share fix summaries with human reviewers

Inspect GitHub and GitLab repositories, issues, and proposed code changes, then prepare small fixes with tests and review summaries. Uses existing command-line authentication and requires approval before publishing changes or modifying repository records.

• Review open issues and proposed code changes
• Summarize changes using commit history
• Prepare and test a small code fix

Take an agreed code change through a GitHub or GitLab pull request, automated checks, independent review, and fixes. Merge only after the latest commit passes all checks and has no unresolved review findings.

• Turn an agreed code change into a pull request
• Wait for automated checks and investigate failures
• Arrange an independent review and address findings

Design automated build, test, and deployment workflows for GitHub Actions, GitLab CI/CD, and Jenkins. Covers job ordering, dependency caching, secret handling, and gradual releases that use health checks before expanding deployment.

• Automating builds, tests, and deployments
• Reducing pipeline time with caching and parallel jobs
• Planning gradual releases and rollbacks

Configure GitLab CI/CD pipelines and runners for automated building, testing, and deployment. Create .gitlab-ci.yml configurations, manage runners, and implement DevOps workflows. Use when working with GitLab repositories or self-hosted GitLab instances.

The English summary is being prepared. Showing the original description.

GitLab CLI for managing issues, merge requests, CI/CD pipelines, and repositories. Use when: (1) Creating, reviewing, or merging MRs, (2) Managing GitLab issues, (3) Monitoring or triggering CI/CD pipelines, (4) Working with self-hosted GitLab instances, (5) Automating GitLab workflows from the command line. Requires GITLAB_TOKEN (recommend minimal scopes). The `glab api` command enables arbitrary API calls - use read-only tokens when possible.

The English summary is being prepared. Showing the original description.

Generate and optimize CI/CD pipelines for GitLab CI and CircleCI. Use when a user asks to set up GitLab CI, create a CircleCI pipeline, build a CI pipeline for GitLab, automate deployments with CircleCI, add test automation to GitLab, or configure continuous integration on non-GitHub platforms. For GitHub Actions pipelines, use the github-actions skill instead.

The English summary is being prepared. Showing the original description.

Use when designing or validating GitLab CI/CD and automatic release lifecycles, inspecting pipeline and job state read-only, composing non-interactive merge-request commands, or setting up protected refs and release credentials. Also covers reusable components and inputs, GitLab Functions, gitlab-ci-local, glab command composition, and GitLab Flavored Markdown. For pipeline execution or retry requests, provide inspection and command drafting while leaving execution to the operator.

The English summary is being prepared. Showing the original description.

Use this skill when authoring or debugging GitLab CI/CD pipelines (.gitlab-ci.yml) — e.g. "add a CI pipeline for this Drupal project", "run phpcs/phpstan/phpunit in GitLab CI", "deploy with drush from a pipeline", "why is my job not running", "cache composer dependencies", or anything involving stages, rules, artifacts, environments, or GitLab runners.

The English summary is being prepared. Showing the original description.

スケーラブルな自動化のためのマルチステージワークフロー、キャッシング、分散ランナーを備えたGitLab CI/CDパイプラインを構築。GitLab CI/CDの実装、パイプラインパフォーマンスの最適化、または自動テストとデプロイメントのセットアップ時に使用。

The English summary is being prepared. Showing the original description.

Review GitHub pull requests and GitLab merge requests for security, test gaps, compatibility, and performance risks. Trace affected code and services, then produce a prioritized report with suggested fixes and a structured review checklist.

• Reviewing shared libraries and API changes before merging
• Organizing feedback on large pull requests
• Checking authentication and payment code changes

Set up Git workflows for Gitee, Coding.net, 极狐 GitLab, and CNB with platform-specific connection and authentication examples. Choose branching rules, standardize Chinese commit messages, and adapt automated testing and deployment configurations to your team's workflow.

• Configure connections and authentication for Chinese Git platforms
• Choose branching rules that fit the team
• Standardize Chinese commit messages and review templates

Assess security weaknesses in CI/CD systems that automate software builds and delivery. Covering GitHub Actions, Jenkins, GitLab CI, and Azure DevOps, the skill examines unsafe inputs, excessive permissions, exposed credentials, and tampered build outputs, alongside detection and defensive controls.

• Reviewing workflow inputs and execution triggers
• Assessing pipeline permissions and credential exposure
• Checking build artifact handoffs for tampering risks

Read and write GitLab: your user, projects, open merge requests, create issues. Trigger phrases: gitlab, merge request, gitlab issue.

The English summary is being prepared. Showing the original description.

GitLab CI migration to GitHub Actions — syntax mappings and the migration report template for Pipelines, includes, Pages, environments, rules/only/except, parallel jobs, GitLab-specific variables. Load with `migration-core` when migrating GitLab CI sources to GitHub Actions.

The English summary is being prepared. Showing the original description.

Prepare a repository for engineering skills by documenting where issues are tracked, which triage labels organize incoming work, and where glossaries and architecture decision records belong. Review the existing setup and confirm drafts before writing configuration files.

• Prepare a repository before using engineering skills
• Document the issue tracker and triage labels
• Set rules for glossary and architecture decision record locations

Build workflows that generate changelogs and release notes from commits, pull requests, and releases. Use Keep a Changelog formatting, standardize commit messages with Conventional Commits, and manage version numbers through Semantic Versioning rules.

• Automating changelog generation from commits and pull requests
• Standardizing team commit messages
• Setting up GitHub or GitLab release notes