Loading...
Loading...
Found 1,865 Skills
Interact with GitLab via the glab CLI. Supports five MR workflows — Read (summarize), Review (full code/security/QA review), Fix (review + implement), CI Fix (fix pipeline failures), and Feedback (address review comments). Trigger whenever the user provides a GitLab MR URL or says anything like "อ่าน MR", "ดู MR", "check MR", "review MR", "ช่วย review MR นี้", "ตรวจ MR", "แก้ตาม MR", "fix MR", "fix CI", "fix pipeline", "แก้ pipeline", "แก้ตาม comment", "แก้ตาม feedback", "address feedback", or just pastes a GitLab MR URL. Also supports listing MRs, viewing MR status, checking CI/CD pipelines, approving MRs, and other glab operations. Trigger on "check pipeline", "list open MRs", "pipeline failed", or any GitLab-related task.
Create GitHub PRs with structured title and body. Use when: opening PRs, creating pull requests after pushing. Triggers: /git-pr-create, create PR, open pull request.
Scan open GitHub issues, PRs, discussions. Produce prioritized triage report with engagement metrics and recommended actions
Interact with GitHub issues - create, list, and view issues.
Use this skill to detect potential secret and privacy leaks in changed files, staged diffs, commit messages, and git identity settings before code is shared or merged.
Flux GitOps patterns for the homelab Kubernetes platform using ResourceSets. Use when: (1) Adding new Helm releases or applications to the platform, (2) Deploying a new service to Kubernetes, (3) Debugging Flux reconciliation issues or sync problems, (4) Understanding ResourceSet patterns, (5) Configuring Kustomizations and variable substitution, (6) Questions about helm-charts.yaml or platform structure, (7) GitOps workflow questions. Triggers: "add helm release", "deploy to kubernetes", "add new service", "add application", "flux resourceset", "flux reconciliation", "flux not syncing", "flux stuck", "gitops", "helm-charts.yaml", "platform values", "flux debug", "HelmRelease not ready", "kustomization", "helmrelease", "add chart", "deploy helm chart"
Automatically diagnose and fix CI failures in the current PR. Retrieves failed logs from GitHub Actions, categorizes the failure (lint, format, type-check, test), applies targeted fixes, verifies locally, and commits/pushes. Use when CI fails after push.
GitHub DNS Fix Assistant. Resolve GitHub access issues. Use this skill when users encounter problems such as inability to access GitHub, DNS resolution failure, connection timeout, etc.
Capture architectural decisions and changes made during a GSDL project into a structured markdown document. Analyzes git history and diffs, extracts key decisions, and optionally pushes the doc to Slite or Notion as a child page. Called by the gsdl orchestrator after all implementation tasks are complete.
Generates detailed, architect-quality GitHub issues from short instructions. Analyzes the project's actual stack, architecture, and codebase before writing. Detects duplicate issues with intelligent multi-strategy search, validates and creates labels, enforces title conventions, controls scope, and publishes via `gh` CLI with robust error handling. Use this skill whenever the user wants to create a GitHub issue, report a bug, propose a feature, request a refactor, or file any kind of technical issue — even if they just say something brief like "we need to fix the auth flow" or "create an issue for X". Also triggers on: "open an issue", "file a bug", "I want to propose...", "add this to the backlog", "gh issue", or any request that implies creating a trackable work item on GitHub.
Saves, retrieves, and searches structured context (reasoning, decisions, trade-offs) behind AI-generated code, linked to git commits. Use when the developer says "save this session with GitWhy", asks about past context or decisions, or wants to push context to a PR. Also use after significant implementation work, debugging sessions, or architecture decisions.
Pull all file comments from the current GitHub pull request and address them by making code changes.