菜单
Authoring and validating GitLab CI configuration. Use when editing `.gitlab-ci.yml`, structuring pipeline stages and jobs, or running `glab ci lint`. For pipeline/job failure investigation, use gitlab:ci-monitor.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Query Claude Code session history via a DuckDB index over `~/.claude/projects/`. Use when asked about Claude Code activity ("how many tokens today?", "what did I work on this week?") or instead of reading, grepping, or jq-ing session transcripts. Not for codebase search, git log queries, or arbitrary databases.
Creating and optimizing Claude Code Skills including activation patterns, content structure, and development workflows. Use when creating new skills, converting memory files to skills, debugging skill activation, or understanding skill architecture and best practices.
Read and query Things 3 data (lists, todos, projects, tags, logbook). Not for writes. Use things:url to create/update, things:inbox for quick captures.
Triage and batch-implement Claude-tagged Things todos as PRs for the claude config repo, discover improvement candidates from session history, or watch open PRs to implement review feedback and close shipped todos. Use when the user wants to work on their Claude Code improvement backlog, process Things todos tagged claude-code, batch-implement configuration changes, mine session history for grounded config-change candidates (Discover mode), or watch this skill's open PRs for review feedback and merges (Watch mode).
Fetch, reply to, and resolve review threads on a GitHub pull request. Use when checking what review feedback needs addressing, whether threads are resolved, replying to review comments, or clearing AI-reviewer threads after acting on them.
Live tmux inbox for reviewing inbound pull requests across GitHub and GitLab. Use when reviewing multiple PRs, checking the review queue, batch reviews, or managing your review inbox. Pass --queue to spawn an already-ordered queue.
| name | gitlab:ci |
| description | Authoring and validating GitLab CI configuration. Use when editing `.gitlab-ci.yml`, structuring pipeline stages and jobs, or running `glab ci lint`. For pipeline/job failure investigation, use gitlab:ci-monitor. |
Working with GitLab CI/CD pipelines and jobs via glab ci.
glab ci status # Pipeline status for current branch
glab ci list # List recent pipelines
glab ci lint # Validate .gitlab-ci.yml
glab ci trace <job-id> # Watch job logs in real-time
glab ci retry <job-id> # Retry a failed job
glab ci run # Trigger pipeline for current branch
Use glab ci --help and glab ci <command> --help for full options.
glab ci view - Interactive view of pipeline jobs (trace/retry from here too)glab ci trace <job-id> - Stream job logs in real-timeglab ci retry <job-id> - Retry a failed jobFor .gitlab-ci.yml syntax, see /ci/yaml/ in GitLab docs.