Dev Guide Repo Watch
Productivitydev-guide-repo-watchDev Guide Repo Watch is an Agent Skill for productivity published in the Lingtai-AI/lingtai repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Read-only workflow for sweeping the Lingtai-AI GitHub org for open issues, open PRs, and recent activity. Use this when a LingTai developer/operator asks what changed across the org, wants to monitor non-self PRs/issues, or needs an idempotent repository-health digest. This is a nested lingtai-dev-guide reference, not a top-level intrinsic skill.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/Lingtai-AI/lingtai/blob/HEAD/tui/internal/preset/skills/lingtai-dev-guide/reference/repo-watch/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/dev-guide-repo-watch, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
LingTai Repo Watch
This nested reference is a read-only developer workflow for sweeping the
Lingtai-AI GitHub org. It is intentionally under lingtai-dev-guide because it
is LingTai-project-specific; it should not be installed as a kernel intrinsic
capability for every agent.
Boundaries
- Read-only by default: do not comment, label, assign, close, merge, or edit GitHub state unless the human explicitly asks for that side effect.
- Report facts with source URLs and timestamps.
- Prefer one concise digest over piecemeal alerts unless the human requested a live monitor.
- If automating, store state locally and alert only on changes to avoid spam.
One-shot org sweep
Use gh from a clean shell with GitHub auth already configured.
gh repo list Lingtai-AI --limit 100 \
--json name,visibility,isArchived,pushedAt,url
gh search issues --owner Lingtai-AI --state open --limit 200 \
--json number,title,repository,state,createdAt,updatedAt,author,labels,assignees,url
gh search prs --owner Lingtai-AI --state open --limit 200 \
--json number,title,repository,state,isDraft,createdAt,updatedAt,author,labels,url
gh search prs --json does not support reviewDecision on all installed gh
versions. If review-decision status is needed, fetch it separately for a small
set of PRs with a command/API that supports that field; do not put
reviewDecision in the broad gh search prs field list unless you have verified
that local gh supports it.
Optional filters
For "non-self" monitoring, filter after fetching rather than hard-coding a single human into this workflow. Example for Jason's machine:
# Conceptual filter after JSON fetch, not a GitHub write:
author.login != "huangzesen"
Digest shape
Group output in this order:
- New or updated open PRs — ready vs draft, author, repo, age, URL.
- Open issues — repo, title, author, labels, stale/updated time, URL.
- Recently merged/closed items if the caller asked for recent activity.
- Stale or blocked items — old open PRs, no assignee, labels implying bug or release blocker.
- No-action footer — say explicitly that no GitHub state was changed.
Keep each item compact:
<repo>#<num> — <title> · <author> · opened <relative date> · updated <relative date> · <url>
Cron / LaunchAgent monitor pattern
When the human asks for ongoing monitoring:
- Create a small script under the agent workspace (for example
workspace/lingtai_org_watch/monitor_lingtai_org.py). - Query open issues/PRs with the read-only commands above.
- Store a JSON state file keyed by
issue:<repo>#<num>andpr:<repo>#<num>. - Alert only on new, updated, or closed/removed items.
- Install a macOS LaunchAgent or other host scheduler with explicit logs.
- Record the script, state path, report path, and launchd plist in the agent's durable stores.
Do not embed secrets in the script output or report. If a Telegram bot token is needed for local alerts, read it from the existing local secret file and never print it.
Suggested report template
# LingTai org watch — <timestamp>
Scope: Lingtai-AI, non-archived repos. Filters: <filters>.
GitHub writes: none.
## Changes since last run
- New: ...
- Updated: ...
- Closed/removed from open list: ...
## Open PRs
...
## Open issues
...
## Artifact / state paths
...
Validation
Before claiming the monitor is installed:
- Run the script once without state/notification and confirm
ghexits 0. - Run it once with state enabled and confirm a report file is written.
- If using launchd,
launchctl print gui/$(id -u)/<label>should show the job loaded and the latest exit status 0; stdout/stderr logs should be clean. - Confirm future runs do not resend the baseline unless explicitly requested.