Skills your agents can run
Plug-and-play capabilities — vetted, versioned, and runnable from any Mighty agent.
GitHub API integration with managed OAuth. Access repositories, issues, pull requests, commits, branches, and users. Use this skill when users want to interact with GitHub repositories, manage issues and PRs, search code, or automate workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
Automatically generate changelogs from git commits following Conventional Commits and semantic versioning.
Execute GitLab merge request governance workflows with API-backed automation. Use this skill when Codex needs to (1) review a GitLab merge request against `.yunlian/rules` and create multiline discussion threads for violations, (2) fix a specific GitLab MR discussion thread by creating a commit from the thread guidance, or (3) summarize a closed/merged GitLab merge request using `.yunlian/summary` constraints and publish the summary into project wiki.
Master Git hooks setup with Husky, lint-staged, pre-commit framework, and commitlint. Automate code quality gates, formatting, linting, and commit message enforcement before code reaches CI.
Jujutsu (jj) version control expert. Use when the user asks about jj, jujutsu, workflow isolation, stacking changes, bookmarks, rebasing, conflict resolution, or any VCS operations involving jj. Covers the full jj command surface including workspaces, operation log, revsets, and GitHub/Gerrit integration.
Logic coherence pass for per-H3 section files: enforce a clear paragraph-1 thesis and surface paragraph-island risks (connector stats are diagnostic, not a quota) before merging. **Trigger**: logic polisher, section logic, thesis statement, connectors, 段落逻辑, 连接词, 论证主线, 润色逻辑. **Use when**: `sections/S*.md` exist but read like paragraph islands; you want a targeted, debuggable self-loop before `section-merger`. **Skip if**: sections are missing/thin (fix `subsection-writer` first) or evidence packs/briefs are scaffolded (fix C3/C4 first). **Network**: none. **Guardrail**: do not add new citations; do not invent facts; do not change citation keys; do not move citations across subsections.
Provides comprehensive GitHub operations using the gh CLI and GitHub API. Activates when working with pull requests, issues, repositories, workflows, or GitHub API operations including creating/viewing/merging PRs, managing issues, querying API endpoints, and handling GitHub workflows in enterprise or public GitHub environments.
Manage a local GitHub knowledge base and provide GitHub search capabilities via gh CLI. Use when users ask about repos, PRs, issues, request to clone GitHub repositories, explore codebases, or need information about GitHub projects. Supports searching GitHub via gh CLI and managing local KB with GITHUB_KB.md catalog. Configure via GITHUB_TOKEN and GITHUB_KB_PATH environment variables.
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing...
GitHub Copilot REST API accessible via curl. Use this skill to manage Copilot subscriptions and retrieve usage metrics.
Research GitHub, GitLab, and Bitbucket repositories using DeepWiki MCP server. Use when exploring unfamiliar codebases, understanding project architecture, or asking questions about how a specific open-source project works. Provides AI-powered repo analysis and RAG-based Q&A about source code. NOT for fetching library API docs (use fetching-library-docs instead) or local files.
Comprehensive guide to GPG commit signing. Set up, configure, and troubleshoot GPG commit signing. Fix GPG signing errors, configure passphrase caching, verify commit signatures. Use when working with Git commit signing, GPG keys, commit verification, signature verification, GPG configuration, or when encountering GPG signing errors. Covers Windows (Gpg4win), macOS (GPG Suite), Linux (gnupg), and WSL installation and setup.
Guide for debugging GitHub Agentic Workflows - analyzing logs, auditing runs, and troubleshooting issues
Use when planning commit strategies or determining when to commit changes. Helps developers commit early and often to tell the story of their development process.
Use when a team sees repeated @codex review cycles or Codex Cloud feedback churn and needs root-cause attribution by development stage.
Isolated workspace creation - creates git worktrees with smart directory selection and safety verification for parallel feature development.
Use when running claudikins-kernel:execute, decomposing plans into tasks, setting up two-stage review, deciding batch sizes, or handling stuck agents — enforces isolation, verification, and human checkpoints; prevents runaway parallelization and context death
Bug reporting protocol for PM and agents to file GitHub issues
Proactive code quality review. Triggers on significant code changes to check security, performance, architecture, and project patterns.
Create governance models and structures for open source projects with team-specific templates for small, medium, and large teams, including NASA/government compliance guidance