4.1K skills · sorted by relevance
Prioritize open LinkedIn integration issues and pull requests, or proposed code changes, using report completeness, severity, reach, and readiness checks. Produce ranked lists, identify missing evidence, and recommend concrete next steps for maintainers.
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, manage repository labels, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "create a label", "rename a label", "list repo labels", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.
The English summary is being prepared. Showing the original description.
Replicate and validate a GitHub issue by spinning up Archon, analyzing the issue, and systematically testing all described symptoms using browser automation. Use when: User wants to reproduce a bug, validate a GitHub issue, confirm a reported problem, or investigate whether an issue is real before working on a fix. Triggers: "replicate issue", "reproduce issue", "validate issue", "confirm bug", "test issue", "can you reproduce", "try to replicate", "verify the bug". Capability: Checks out main, pulls latest, starts Archon, reads the GitHub issue, then uses agent-browser to systematically test every symptom and produce a findings report. NOT for: Fixing issues (use /archon or /exp-piv-loop:fix-issue), general UI testing (use /validate-ui).
The English summary is being prepared. Showing the original description.
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.
The English summary is being prepared. Showing the original description.
Investigate duplicate OpenClaw pull requests and issues using local history and current GitHub evidence. Organize confirmed or suspected duplicates in prtags, recording the decision, confidence, and reasons for maintainers.
Turn a vague request into a precise specification through five phases and file it as a GitHub issue. Optionally start a Claude Code agent in a separate working directory to begin implementation.
Create and organize GitHub issues with templates, labels, assignees, and milestones. Coordinate multiple agents to track progress, post updates, and manage related issues across repositories as part of a shared project workflow.
Organize GitHub issues, synchronize project boards, and plan sprints, or short work cycles. Coordinate multiple AI agents to break issues into tasks, assign work, update progress, and track dependencies across a project.
Prepare repository contributions by checking existing guidelines, related issues, branch naming rules, commit formats, and pull request templates. Organize changes into logical commits and assemble submissions that follow the project's documented contribution process.
Connect NanoClaw to GitHub through Chat SDK so an agent can join pull request and issue comment threads. The skill covers a dedicated bot account, event notifications, access controls, and separate conversation sessions for each thread.
Review open Mastra GitHub issues and trace reported defects to source code. Apply the @mastra/core label to confirmed core bugs, report uncertain ownership, and summarize whether fixes are active, stale, or unclaimed.
Turn a named NemoClaw issue into an implementation plan with clear ownership, scope, completion criteria, and validation evidence. For larger changes, define independently useful steps, their dependencies, and delivery order.
Review open GitHub issues and pull requests against project templates and contribution guidelines. Get a report on missing information and compliance, with options to apply recommended labels or close incomplete submissions with an explanatory comment.
Turn a Bifrost PR or GitHub issue into API regression tests that catch recurring bugs. Review existing coverage, add cases to the Postman collection, and validate collection processing and provider filtering.
Manage GitHub pull requests, which propose code changes, and issues through a central MCP server. Create and update records, add comments, request reviewers, check changed files and automated checks, and merge pull requests.
[omh] Chat report that should become a GitHub issue: turn a public chat report into a confirmed, verified issue package. Use when the user says: github-issue-intake, github issue intake, issue intake, file this as an issue, file a github issue, open a github issue, create a github issue, submit a github issue.
The English summary is being prepared. Showing the original description.
Turn a rough idea, a bug, or a batch of unsolved problems into well-structured GitHub issue(s) and file them with `gh`, auto-classifying type + labels from the content (recommend, then confirm) and following Rove's conventions (beginner-friendly framing, concrete file pointers, an acceptance checklist, zero AI/Anthropic attribution). Handles single, batch, and "file the unsolved problems" modes. Use when the user says "file an issue", "open a GitHub issue", "draft a good first issue", "batch these as issues", "上报 issue", "提个 issue", "报个 bug", "把没解决的发上去", or wants to hand low-priority tasks to outside contributors. Distinct from the daemon-owned internal issue store (`rove api issue-*`); this skill is for outward-facing GitHub issues.
The English summary is being prepared. Showing the original description.
GitHub Issue を読み込み、`_/local-plans/<issue-number>-<slug>.md` に詳細計画を作成して**ユーザー承認後**にコードを実装する。実装後はセキュリティレビュー (OWASP Top 10) → テスト実行 → Conventional Commits でコミット。Issue 番号や URL を渡された実装依頼、「Issue #N を実装して」「この Issue を着手」などで使用。
The English summary is being prepared. Showing the original description.
このセッションで関わった issues/ の .md に更新漏れが無いかを点検し、あれば本文へ書き戻す。「issue の更新漏れない?」「issue 更新した?」「書き戻し漏れ」「/issue-writeback」で発火。完了検出と done/ への移動は issue-sync の担当で、この skill はファイルを動かさない。
The English summary is being prepared. Showing the original description.
Prepare an agent activity transcript for a GitHub pull request or issue. Extract relevant prompts, decisions, and results from local logs, remove sensitive material, and preview the edited record before separately authorized publication.
Manage GitHub work with the gh command-line tool, from issues and pull requests, which propose code changes, to reviews and repository management. Follow task-specific workflows and verify checks, merges, and other remote states.
Analyze all open GitHub issues and pull requests, then produce reports backed by links to specific code commits. Assess bugs, feature requests, and merge readiness without changing anything on GitHub.
Work with GitHub issues, pull requests, and automated checks through the gh command-line tool. Inspect failed workflow steps and their logs, retrieve selected fields, and query the GitHub API for data beyond standard commands.
Upload local screenshots, images, PDFs, archives, and videos to GitHub, then embed them in pull requests, issues, or comments. Use gh-attach to obtain attachment URLs and download existing GitHub attachments to a specified local destination.