GitAICodingCrew

Bootstrap the issue triage configuration for a repository by analyzing existing issues, labels, and contributors to generate `.gitlab/issue-triage/config.json` and `.gitlab/CODEOWNERS`. Use when setting up triage automation on a new or existing repository for the first time.

Compare a merge request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during MR review when approved or repository spec context is available.

Create or update a GitLab merge request from a pushed branch after local review, base-branch sync, validation, and issue linking.

Create a product spec from a GitLab issue in this repository by applying the local shared `write-product-spec` workflow with issue context and output paths. Use when an issue should be turned into a product spec artifact stored under `specs/issue-<issue-number>/product.md` and the agent should prepare file changes only, without creating commits or merge requests itself.

Create a technical spec from a GitLab issue in this repository by applying the local shared `write-tech-spec` workflow with issue context and output paths. Use when an issue should be turned into a tech spec artifact stored under `specs/issue-<issue-number>/tech.md` and the agent should prepare file changes only, without creating commits or merge requests itself.

Repo-specific dedupe guidance . Only the categories declared overridable by the core dedupe-issue skill may be specialized here.

Detect duplicate GitLab issues by comparing the incoming issue's title and description against issue candidates provided by the CI job.

Diagnose GitLab CI failures for a MR, branch, pipeline ID, job ID, or GitLab pipeline URL using the GitLab CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate MR build failures.

Create repository-compliant branches with efficient issue naming, base selection, and safety checks.

Create clean, repo-aware commits from real diffs with focused inspection, selective staging, and minimal tool calls.

Create isolated Git worktrees for parallel branch work with efficient naming, base selection, and safety checks.

Implement a GitLab issue in this repository by applying the local shared `implement-specs` CI job with repository-specific issue, spec-context, and summary-file handling. Use when issue details are provided in the prompt and the agent should produce the implementation diff and handoff metadata without creating merge requests itself.

Implement an approved feature from the repository's product and tech specs, keeping specs and code aligned in the same change as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature.

Run the repository MR review CI job locally from the current branch using the same root-level snapshots and review.json contract as CI.

Repo-specific wrapper around the core review-mr workflow for GitLab merge request reviews.

Review a GitLab merge request from pinned `mr_description.txt`, `mr_diff.txt`, and optional `spec_context.md` snapshots, then write and validate `review.json`. Use when a CI job or bot needs offline MR review comments without posting to GitLab.

Run the repository spec review CI job locally from the current branch using the same root-level snapshots and review.json contract as CI.

Repo-specific wrapper around the core review-spec workflow for spec-only merge request reviews.

Review a spec-only GitLab merge request from pinned `mr_diff.txt` and `mr_description.txt` snapshots, then write and validate `review.json` with document-quality findings.

Audit a merge request diff for common security concerns (input validation, sanitization, authentication and authorization, secrets management, unsafe dependencies, and related risks) and fold findings into the same review.json produced by the base MR review. Use as a supplement to `review-mr` whenever a code MR is being reviewed.

Audit a product or tech spec merge request diff for high-level security concerns (threat surface, authentication and authorization model, trust boundaries, sensitive data handling, secrets and key management, dependency posture, and abuse or misuse cases) and fold findings into the same review.json produced by the base spec review. Use as a supplement to `review-spec` whenever a spec MR is being reviewed.

Drive a spec-first CI job for substantial features by writing a product spec before implementation, writing a tech spec when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.

Repo-specific triage guidance. Only the categories declared overridable by the core triage-issue skill may be specialized here.

Triage a newly filed GitLab issue in this repository by analyzing the report, inspecting relevant code, estimating reproducibility, suggesting the likely root cause, and returning structured triage output without mutating GitLab directly.

Learn repo-local duplicate issue guidance from recent maintainer duplicate closures and propose updates to the dedupe companion skill.

Improve repo-local MR review companion skills from human feedback on bot reviews. Use when updating review guidance from recent GitLab MR review feedback.

Write a product spec for a significant user-facing feature in this repository, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.

Write a tech spec for a significant feature in this repository after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.