Loading...
Loading...
Found 1,511 Skills
This skill should be used when the user asks to "create a pull request", "create PR", "open PR", "update a pull request", "update PR", "create an issue", "file an issue", "create a GitHub issue", "create a Claude Code issue", "report a bug in Claude Code", "create a Codex issue", "report a bug in Codex CLI", "create a Sablier issue", "file an issue in sablier-labs", "create a discussion", "start a GitHub discussion", "yeet a PR", "yeet an issue", "yeet a discussion", or mentions GitHub contribution workflows.
Authors, reviews, installs, and debugs GitHub Agentic Workflows in repositories, including workflow markdown, frontmatter, gh aw compile and run flows, safe outputs, security guardrails, and operational patterns. Use when creating or maintaining GH-AW automation. Don't use for standard deterministic GitHub Actions YAML, generic CI pipelines, or non-GitHub automation systems.
Standardize zenon-red repository structure. Use when setting up a new zenon-red repo or ensuring consistency with organizational standards. Creates repositories from the nexus-template GitHub template, then customizes for the specific project.
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management
Agent skill for github-modes - invoke with $agent-github-modes
This skill should be used when dispatching autonomous development or review tasks from GitHub issues. Covers scanning for new issues with the 'autonomous' label, dispatching dev-new/dev-resume/review processes, dependency checking, retry counting, stale process detection, and concurrency limiting. Use when asked to "run the dispatcher", "scan for pending issues", "dispatch autonomous tasks", "check stale agents", or "set up the dispatch cron".
Debug CI E2E failures from pull requests by inspecting GitHub checks, downloading Playwright reports, and mapping failures to local Nx commands. Use when debugging failed E2E tests in PR workflows.
Generate objective reference check reports about the user from real AI collaboration data — session history, git logs, GitHub profile, and memory files. Like a colleague writing a professional reference, but grounded in actual shared work. Use whenever the user asks to evaluate them as a developer, wants a reference letter, work style analysis, introduced by my agents content, interview prep from collaboration history, or blog topics from past discussions. Triggers on: write a reference, analyze my work patterns, what do you think of me, 나에 대한 레퍼런스 써줘, 내 작업 스타일 분석해줘. Not for general code review, architecture docs, cover letters, or codebase-only analysis.
プロジェクトのドラフトアイテム (DraftIssue) を実 GitHub Issue に変換し、Status/Priority/Size 等のフィールド値を引き継ぐ。親 Issue を指定または新規作成して `gh api .../sub_issues` で sub-issue として紐付け可能。「ドラフトを Issue 化」「DraftIssue を変換」「プロジェクトのタスクを Issue にして」などで使用。
Files structured GitHub bug reports for agent-validator when users ask to file, report, or open an issue for a suspected defect
Daily tech news collection. Search for the latest news in technical fields such as AI, GitHub, frontend, backend, and open-source projects, and generate Chinese summary blog articles. Keywords: news, daily news, tech news, AI news, GitHub trending.
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.