skills.rest
Lingtai-AI
Lingtai-AIOFFICIAL
Explore all skills by this author →
GitHub

dev-guide-repo-watch

Sweep the Lingtai-AI GitHub org for open issues, PRs, and recent activity.

692|60|Updated Mar 15, 2026
Search Tags:#issues#gh CLI#digest#gitHub#launchagent#Pull Requests#Monitoring
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill dev-guide-repo-watch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-guide-repo-watch
Source: https://github.com/Lingtai-AI/lingtai/tree/main/tui/internal/preset/skills/lingtai-dev-guide/reference/repo-watch
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill dev-guide-repo-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

LingTai developers and operators lack a repeatable, read-only way to see what changed across the entire Lingtai-AI GitHub organization without manually checking each repository for open issues, pull requests, and recent activity.

Core Features & Use Cases

  • One-shot org sweep: Uses the GitHub CLI (gh) to list repos, open issues, and open PRs across the Lingtai-AI org with structured JSON output.
  • Digest formatting: Groups results into new/updated PRs, open issues, recently closed items, and stale or blocked items, each with author, age, and URL.
  • Stateful monitoring: Provides a cron/LaunchAgent pattern that stores JSON state and alerts only on new, updated, or closed items to avoid notification spam.
  • Use Case: A maintainer asks what changed across the org this week; the workflow runs the read-only gh queries and returns a single timestamped digest confirming no GitHub state was modified.

Quick Start

Ask the agent to sweep the Lingtai-AI GitHub org and produce a read-only digest of open PRs, open issues, and recent activity.

Frequently Asked Questions about dev-guide-repo-watch

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

FAQPage Schema
How do I list all open issues and PRs across a GitHub organization?▼

Use gh search issues and gh search prs with the --owner flag and --state open, requesting JSON fields like number, title, repository, author, and updatedAt. This returns structured data you can group into a digest by repo, age, and labels.

How to monitor GitHub repos for changes without spamming alerts?▼

Store a JSON state file keyed by issue and PR identifiers, then alert only on new, updated, or closed items between runs. Schedule the script with cron or a macOS LaunchAgent and keep logs for validation.

Does gh search prs support the reviewDecision field?▼

Not on all installed gh versions. Fetch review-decision status separately for a small set of PRs using a command or API that supports that field, and only add reviewDecision to broad searches after verifying local gh support.

Can this workflow modify GitHub issues or pull requests?▼

No, it is read-only by default and does not comment, label, assign, close, merge, or edit GitHub state unless the human explicitly requests that side effect. Every report includes a footer confirming no GitHub writes occurred.

Why does my GitHub monitor resend the same alerts every run?▼

This happens when no state file is persisted between runs, so every item appears new. Store state keyed by issue:<repo>#<num> and pr:<repo>#<num>, and confirm the baseline is not resent unless explicitly requested.

Related Skills

Explore More Software Engineering Skills→
edri2oredri2or

org-skill-pipeline

Automate skill distribution across enrolled GitHub repositories via a three-workflow pipeline.

Official
Advanced
JaviMontanoJaviMontano

apex-issue-management

Log, classify, escalate, and resolve project issues with structured workflows.

Community
Advanced
SeaLion-hubSeaLion-hub

land-and-deploy

Merge pull requests, deploy to production, and verify canary health.

Community
Advanced
finsilabsfinsilabs
44

saleor-development

Develop and extend Saleor commerce platform via GraphQL API and webhooks.

Official
Intermediate