gitlab-ci-kiro-pipeline SKILL.md skillB
gitlab-ci-kiro-pipeline from timwukp/agent-skills-best-practice is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add timwukp/agent-skills-best-practice/gitlab-ci-kiro-pipeline@git:20260702.461c8f1Pins git:20260702.461c8f1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- timwukp/agent-skills-best-practice
- Path
skills/skills/gitlab-ci-kiro-pipeline/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260702.461c8f1, committed Jul 2, 2026
- First version recorded
- Jul 2, 2026
- Size
- 12,684 bytes
- Repository stars
- 12
- License
- MIT
Build, extend, or debug GitLab CI/CD pipelines (.gitlab-ci.yml) that run Kiro CLI in headless mode for AI-powered merge-request review, security scanning, test-failure analysis, config-drift detection, code-duplication sync checks, and change-impact/risk analysis — including integrating the customer's MCP servers (SonarQube SAST, Jira, internal tools) into CI jobs. Use this skill whenever the user mentions GitLab CI, .gitlab-ci.yml, GitLab pipelines, merge-request automation, AI code review in…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# GitLab CI/CD Pipelines with Kiro CLI Headless Mode Build `.gitlab-ci.yml` pipelines where Kiro CLI acts as an AI reviewer/analyst on merge requests. The pattern: each job installs Kiro CLI in a throwaway container, gathers context (the MR diff, config files, failure logs), and runs `kiro-cli chat --no-interactive` with a role-scoped prompt. Output goes to the job log and optionally gates the merge. ## Workflow 1. **Understand the repo and goals.** Ask (or infer from the repo) which checks the user wants: advisory review only, or merge-blocking gates? Which languages/config layouts exist? Is there an existing `.gitlab-ci.yml` to extend? 2. **Pick jobs from the recipe catalog.** Read `references/job-recipes.md` for nine proven job patterns (code review, PII/secrets scan, test-failure analysis, diff issue detection, build-failure remediation, config drift, cross-repo config validation, duplication sync check, change-impact analysis). Copy only the ones the user needs. 3. **Start from the template.** `assets/gitlab-ci-template.yml` is a complete, working pipeline skeleton. Adapt stages and jobs rather than writing from scratch. …
Read the whole file at its exact version.
How to install
mdr add timwukp/agent-skills-best-practice/gitlab-ci-kiro-pipeline@sha256:f39c58315e4a62f2The line at the top of this page pins the label git:20260702.461c8f1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_yd6ewnbin6whun2e)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, all committed on Jul 2, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260702.461c8f1 latest | 2026-07-02 | 461c8f1 | 12,684 B | B | view · diff |
| git:20260702.81f2cc2 | 2026-07-02 | 81f2cc2 | 12,160 B | B | view · diff |
| git:20260702.4e0c630 | 2026-07-02 | 4e0c630 | 11,694 B | B | view |
Audit of the latest version
- fail: No curl or wget piped into a shell (matched: curl -fsSL https://cli.kiro.dev/install | bash)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12684 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
timwukp/agent-skills-best-practice · 12 stars · license MIT · pushed 2026-09-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yd6ewnbin6whun2e GET https://markdownregistry.com/api/v1/resolve?ref=timwukp/agent-skills-best-practice/gitlab-ci-kiro-pipeline GET https://markdownregistry.com/api/v1/blob/f39c58315e4a62f25d1a4dc0104c62b364399106b42657d065553557438776df
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.