Gitlab Issue From Review

GitLab Issue from Code Review

Create GitLab issues from code review findings for tracking and remediation.

Prerequisites

Before executing this skill, ensure:

1. Code review findings are available in context
2. The GitLab connection is configured with API access
3. The target project {{config.project_path}} exists and is accessible

Setup

Source the GitLab helper functions:

source ./_skills/connections/gitlab/gitlab/scripts/gitlab_helpers.sh
PROJ=$(gitlab_project_id "{{config.project_path}}")

Workflow

Step 1: Get Project ID

PROJ=$(gitlab_project_id "{{config.project_path}}")

If the project is not found, report the error with the configured path.

Step 2: Extract Review Findings

From the code review context, extract each finding:

Step 3: Classify and Label Each Finding

Map review findings to GitLab labels:

Severity labels:

Category labels:

Step 4: Format Issue Description

For each finding, structure the issue description:

## Code Review Finding

**Source:** MR !{mr_number} (if available)
**File:** `{file_path}:{line_number}`
**Severity:** {severity}
**Category:** {category}

---

## Description

{detailed explanation of the finding, why it is problematic, and what risk it introduces}

## Code Reference

The issue was identified in [`{file_path}`]({link_to_file}#L{line_number}):

\`\`\`{language}
{code_snippet_with_issue}
\`\`\`

## Suggested Fix

{description of the recommended approach to resolve the issue}

\`\`\`{language}
{suggested_code_fix}
\`\`\`

## Acceptance Criteria

- [ ] The identified issue is resolved
- [ ] Fix does not introduce regressions
- [ ] Relevant tests are added or updated
- [ ] Changes are reviewed and approved

Step 5: Create the GitLab Issue

gitlab_create_issue $PROJ \
  --title "[Code Review] ${finding_title}" \
  --description "${formatted_description}" \
  --labels "code-review,${severity_label},${category_label}"

Step 6: Link to Source MR (Optional)

If the finding originated from a specific merge request, add a comment on the MR referencing the created issue:

gitlab_create_mr_discussion $PROJ $MR_IID \
  "Created tracking issue #${issue_iid} for this code review finding: ${finding_title}"

Batch Processing

When multiple findings exist from a single review, process them efficiently:

1. Group findings by severity (Critical first, then High, Medium, Low)
2. Create issues sequentially to avoid rate limits
3. Report a summary table after all issues are created

Summary Output Format

| # | Issue | Severity | Category | File |
|---|-------|----------|----------|------|
| 1 | #123 - SQL injection risk | Critical | Security | src/db/query.py:45 |
| 2 | #124 - Missing null check | High | Bug | src/api/handler.py:112 |
| 3 | #125 - N+1 query pattern | Medium | Performance | src/services/user.py:78 |

Output

After successful creation, report:

1. Number of issues created
2. Summary table with issue numbers, titles, severity, and links
3. Any findings that could not be converted to issues (with reasons)
4. Link back to the source MR if applicable

Error Handling

Issue Title Convention

Prefix all issue titles with [Code Review] for filtering:

• [Code Review] SQL injection vulnerability in user query
• [Code Review] Missing error handling in payment flow
• [Code Review] Unused import increases bundle size

Guidelines

• One issue per distinct finding (do not combine unrelated findings)
• Include enough code context for someone unfamiliar with the review to understand the issue
• Link to the specific file and line in the repository
• Set severity labels accurately based on the review finding's impact
• Add acceptance criteria that define what "done" looks like
• Reference the originating MR in the issue description when available

Counter-Rationalizations