Communication & Collaboration Agent Skills for Grok Build

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already…

Determine which PostHog team owns a file, directory, or code path, or enumerate all code a team owns (via distributed `owners.yaml`…

Printing Press CLI for Etherpad. Etherpad is a real-time collaborative editor scalable to thousands of simultaneous real time users. It…

Inspect, triage, and actively maintain all open GitHub issues and pull requests across public, non-archived, non-fork eunomia-bpf…

Use when shaping team structure — functional vs squad, span-of-control, reorg cost, Conway-aware boundaries.

Review a solution and identify risks, tests, and practical improvements.

Generates a reviewer-facing HTML explanation page for the current branch's pull request, publishes it to gh-pages for public repositories…

Reviews F# code changes for functional idioms, type safety, security vulnerabilities, and runtime performance.

Feishu cloud-storage and comment workflows.

Keep a PR merge-ready by triaging comments, resolving clear conflicts, and fixing CI in a loop.

Review code, PRs, diffs, or implementation plans for distributed-systems risks, HTTP API contracts, queue consumers, scheduled jobs, and…

Draft a Feature Requirements Document (FRD) using the Overview / Terminology / Requirements template, Product Overview context…

Architecture decision-debt scanner — decisions never made explicitly or silently contradicting each other across SCOPE/PLAN/code/history…

Push committed changes and create a draft PR on GitHub.

Fetch and summarize review comments from the active pull request

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.

Finds real correctness bugs in code changes.

Verify whether a GitHub issue is implemented in the current codebase by collecting evidence from the GitHub issue, git history, docs…

GitHub contributor context: identity, activity, trust, company/team signal.