toddsmithsalter/dotfiles/fix-gitlab-issue

Claude Code and agent skill by toddsmithsalter/dotfiles

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Fix Gitlab issues using glab CLI. Use when asked to fix, resolve, or address a Gitlab issue. Creates fixes on separate branches, runs tests locally, and creates MRs when tests pass. Requires glab CLI authenticated and repo cloned locally.

Install

npx vskill@latest install toddsmithsalter/dotfiles/fix-gitlab-issue

SKILL.md

Gitlab Issue Fixer

Fix Gitlab issues by implementing solutions on feature branches with proper testing.

Prerequisites

  • glab CLI installed and authenticated
  • Repository cloned locally
  • Test command available (auto-detected or specified)

Workflow

1. Understand the Issue
bash
glab issue view <issue-number>

Read the issue thoroughly.

2. Create Feature Branch
bash
git checkout main && git pull origin main
git checkout -b fix-<short-description>

Branch naming: fix-description (lowercase, hyphens).

3. Analyze the Codebase

Before coding, understand the relevant parts:

  • Locate files related to the issue
  • Check existing tests for patterns
  • Review any referenced code in the issue
4. Implement the Fix

Make minimal, focused changes that address the issue. Follow existing code style and patterns.

5. Run Tests Locally

Detect and run the test suite. Most likely it will be pest or phpunit. Take a look what is defined in composer.json or the testing github file.

Tests must pass locally before proceeding. If tests fail:

  1. Analyze failures
  2. Fix the implementation
  3. Re-run until all pass
6. Commit Changes
bash
git add -A
git commit -m "Fix #<issue-number>: <concise description>"

Use conventional commit message referencing the issue number.

7. Push and Create MR
bash
git push -u origin fix/issue-<issue-number>-<short-description>
gh pr create --title "Fix #<issue-number>: <title>" --description "Fixes #<issue-number>
## Changes
- <bullet points of changes>
## Testing
- All local tests pass
- <any additional testing done>"
8. Monitor CI
bash
glab ci status --live

If CI fails:

  1. Review the failure: glab ci view --pipelineid <pipeline-id>
  2. Fix locally
  3. Push additional commits
  4. Repeat until CI passes

Quick Reference

bash
# View issue
glab issue view 123
# Create branch
git checkout -b fix/issue-123-description
# After fixing and tests pass
git add -A && git commit -m "Fix #123: description"
git push -u origin fix/issue-123-description
glab mr create --fill
# Watch CI
glab ci status --live

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/toddsmithsalter/dotfiles/fix-gitlab-issue/badge)](https://verified-skill.com/skills/toddsmithsalter/dotfiles/fix-gitlab-issue)

Something wrong with this skill or its page? Tell us.