repo-watch
Detect active repos by the owner not cloned locally and request confirmation before acting
What this skill does
# Repo Watch
## Accounts
Read `bot_account`, `owner_account` from the org's CLAUDE.md `## Automation config` table.
## Purpose
Detect GitHub repos where the owner has active work (issues, PRs, reviews) that are not cloned locally.
For each discovered repo, open an issue asking for confirmation before cloning.
## Helper script
```bash
~/.claude/scripts/repo-watch.sh [org-name ...] > /tmp/repo-watch.json
```
If the script is missing, run `/setup-scripts` to regenerate it.
The script outputs a JSON object with `missing_repos` array, each containing:
- `org`, `gh_org`, `repo`, `last_push`, `open_issues_assigned`
## Phase 1: Run script and review
Parse the JSON output.
Skip repos that are already listed in the org's CLAUDE.md under `## Excluded repos`.
## Phase 2: Confirm with owner
For each missing repo, **do not clone automatically**.
Instead, create a GitHub issue on the repo asking for confirmation:
```bash
gh issue create -R {gh_org}/{repo} \
--title "Add to local dev environment?" \
--body "The bot detected that the owner has active work on this repo but it's not in the local dev setup.
Should I clone this repo and add it to the org automation?
- React with ๐ to confirm
- React with ๐ to exclude (will be added to the exclusion list)
This was opened by a bot. Please ping the owner for any questions."
```
## Phase 3: Check for responses
On subsequent runs, check for reactions on previously opened issues:
- ๐ โ clone the repo and add to CLAUDE.md
- ๐ โ add to `## Excluded repos` in CLAUDE.md and close the issue
```bash
# Use the owner_account from Automation config
gh api "repos/{gh_org}/{repo}/issues/{number}/reactions" \
--jq '[.[] | select(.user.login == "<owner_account>")] | .[0].content'
```
## Phase 4: Clone confirmed repos
For repos confirmed with ๐:
1. Clone: `gh repo clone {gh_org}/{repo} $CODE_DIR/{org}/{repo}`
2. Add to the org's CLAUDE.md local repos table
3. Close the issue with a comment
## Phase 5: Update exclusions
For repos rejected with ๐:
1. Add to `## Excluded repos` section in the org's CLAUDE.md
2. Close the issue with a comment
## Auto-Exit When Standalone
**IMPORTANT**: If this command is being run as a standalone request, automatically exit after completing all phases successfully.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.