Installation

Install han binary (required for hooks to work):

curl -fsSL https://han.guru/install.sh | bash

Then install this plugin:

han plugin install jutsu-gitlab-ci

Overview

Validation and quality enforcement for GitLab CI/CD pipeline configurations.

What This Jutsu Provides

Validation Hooks

GitLab CI Lint: Validates .gitlab-ci.yml syntax using glab ci lint

Skills

This jutsu provides the following skills:

Pipeline Configuration: Stages, workflow rules, DAG pipelines, includes
Job Configuration: Scripts, environments, rules, parallel execution
Variables & Secrets: CI/CD variables, secret management, OIDC
Artifacts & Caching: Build artifacts, cache strategies, optimization
CI/CD Best Practices: Pipeline optimization, security, organization

Installation

Install via the Han marketplace:

han plugin install jutsu-gitlab-ci

Usage

Once installed, this jutsu automatically validates your GitLab CI configuration:

When you finish a conversation with Claude Code
When Claude Code agents complete their work

Requirements

glab CLI installed and authenticated
GitLab project with .gitlab-ci.yml

Contributing

See CONTRIBUTING.md for guidelines.

License

MIT License - See LICENSE for details.

Skills

📖

gitlab-ci-artifacts-caching

Use when configuring artifacts for inter-job data passing or caching for faster builds. Covers cache strategies and artifact management.

📖

gitlab-ci-best-practices

Use when optimizing GitLab CI/CD pipelines for performance, reliability, or maintainability. Covers pipeline optimization and organizational patterns.

📖

gitlab-ci-job-configuration

Use when defining GitLab CI jobs, configuring scripts, setting up environments, or managing job dependencies. Covers job structure and execution options.

📖

gitlab-ci-pipeline-configuration

Use when configuring GitLab CI/CD pipelines, defining stages, or setting up workflow rules. Covers pipeline structure, stage ordering, and execution flow.

📖

gitlab-ci-variables-secrets

Use when configuring GitLab CI/CD variables, managing secrets, or integrating with external secret providers. Covers secure credential handling.

Hooks

⚠️

Token Usage Notice

Hooks run automatically during Claude Code sessions and their output is sent to the model for processing. This may increase token usage and associated costs. Consider disabling hooks you don't need via han-config.yml.

🛑

Stop

Runs when the main Claude Code agent has finished responding. Can verify task completion, check quality gates, or ensure documentation requirements are met before the session ends.

🛑

SubagentStop

Runs when a Claude Code subagent (Task tool call) has finished responding. Can validate subagent outputs, enforce quality standards, or trigger additional workflows after delegated tasks complete.