skills.rest
Caldis
CaldisCOMMUNITY
Explore all skills by this author →
Website𝕏@Caldis_ChenGitHub

community-pr-loop

Manages the full lifecycle of community pull requests from triage through post-release issue notification.

21.3k|683|Updated Jan 27, 2017
Search Tags:#open source#release notes#triage#gitHub#MacOS#Code review#Pull request
One-click install
npx skills add https://github.com/Caldis/Mos --skill community-pr-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: community-pr-loop
Source: https://github.com/Caldis/Mos/tree/main/.agents/skills/community-pr-loop
Command: npx skills add https://github.com/Caldis/Mos --skill community-pr-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers of the Mos macOS input-interception tool face high-risk external contributions touching event taps, HID devices, and accessibility permissions, and need a disciplined end-to-end process for reviewing, merging, releasing, and following up on community PRs without regressions or neglected contributors.

Core Features & Use Cases

  • Structured PR triage and cross-branch analysis: Classifies open PRs (bug fix, feature, dependency bot) and checks whether bugs exist on both master and active refactor branches before deciding merge strategy.
  • Deep review with domain checklists: Enforces specialized review criteria for event tap changes (CGEventTapLocation, event masks, synthetic event loops, secure input) and performance red lines for Logi/HID++ code, with three outcomes: merge with thanks, request-changes with actionable guidance, or close with acknowledgment.
  • Release integration and post-release follow-up: Writes plain-language release notes with inline contributor credits, then revisits every related issue (including same-symptom duplicates) to notify reporters and request verification.
  • Use Case: When asked to "see which PRs need handling", the Skill scans all open PRs, cross-analyzes branches, reviews event-tap-sensitive diffs against the checklist, merges safe fixes with personalized thank-you comments, and after release notifies every linked issue reporter.

Quick Start

Ask the assistant to scan the open PRs in the Mos repository and run the full community PR loop from triage through review and merge recommendations.

Frequently Asked Questions about community-pr-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review and merge community pull requests on GitHub?▼

Use gh pr list to triage open PRs by type, read the full diff, verify tests genuinely fail-then-pass, then squash merge with a personalized thank-you comment. This Skill codifies that workflow with checklists specific to input-event code.

How should maintainers handle PRs that touch macOS event taps?▼

Review tap location, options, event masks, and lifecycle changes against a dedicated checklist covering annotation layer semantics, synthetic event loop guards, secure input boundaries, and blocking callback latency. Such changes require beta-channel exposure before stable release.

What should release notes for behavior changes include?▼

Release notes should use plain language without technical jargon, credit contributors inline with their verified GitHub login, and pin a behavior-change notice at the top describing the change from the existing user's perspective.

How do I notify issue reporters after a fix ships?▼

Collect issues from PR body keywords like Fixes #N, search for same-symptom duplicates, and comment on each with the reporter's handle, what was fixed, contributor credit, the release link, and a request to verify. Match the reporter's language.

When should a pull request be rejected despite fixing a real bug?▼

Reject implementations that violate performance red lines, such as repeatedly sending HID++ requests over time, regardless of how real the bug is. Prefer discrete event-driven, one-shot probe-then-repair approaches instead.

Related Skills

Explore More Software Engineering Skills→
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
eugene1geugene1g
1.9k

release

Automate Agent Safehouse releases by inspecting commits, proposing SemVer versions, drafting changelogs, and publishing GitHub releases and Homebrew taps.

Community
Advanced
paperclipaipaperclipai
79.8k

qa-acceptance

Generate structured acceptance criteria and validation plans for feature changes and software releases.

Official
Intermediate
Tencent-HunyuanTencent-Hunyuan
890

code-standards

Enforce coding standards and review-driven workflows for Python, PyTorch, shell scripts, and configs.

Official
Advanced