00406.r17House 304CodingSep 9, 202600406

Monitor a Public Code Repository

A public log of a finished bot job — verified, serialized, and open to patch.

Read the articleNot allowed to say hiJob breakdowns

Prompt (copy into Grok)

1. Connect to a public code repository service. 2. Search for a specified repository. 3. Collect the repository's URL. 4. Check the repository's live site at regular intervals. 5. Determine if any changes have been made since the last check.

Job

What was asked

1. Connect to a public code repository service. 2. Search for a specified repository. 3. Collect the repository's URL. 4. Check the repository's live site at regular intervals. 5. Determine if any changes have been made since the last check.

Outcome

What happened

A person created a bot to monitor a public code repository by using a connector to find the repository and checking the live site for changes. This job is the public pattern.

Guardrails

Constraints

repo: https://github.com/leoduquesnel/myrepo

Run again

Would they run this again?

Yes

Connectors

Tools this job touched

GitHub

Evidence

Proof attached to this serial

https://x.com/LeoDuquesnel/status/2097723997450633605 — Imported from the X post tagged for @grokbotsh.

Changelog

Revisions on this serial

r1Filed.Sep 9, 2026
r2QA revisit: more from the source thread.Sep 9, 2026
r3Public job and prompt from the specific filing.Sep 9, 2026
r4Public job and prompt from the specific filing.Sep 10, 2026
r5Public job and prompt from the specific filing.Sep 11, 2026
r6Public job and prompt from the specific filing.Sep 12, 2026
r7Public job and prompt from the specific filing.Sep 13, 2026
r8Public job and prompt from the specific filing.Sep 14, 2026
r9Public job and prompt from the specific filing.Sep 15, 2026
r9Public job and prompt from the specific filing.Sep 15, 2026
r10Public job and prompt from the specific filing.Sep 16, 2026
r10Public job and prompt from the specific filing.Sep 16, 2026
r11Public job and prompt from the specific filing.Sep 17, 2026
r11Public job and prompt from the specific filing.Sep 17, 2026
r12Public job and prompt from the specific filing.Sep 18, 2026
r13Public job and prompt from the specific filing.Sep 19, 2026
r13Public job and prompt from the specific filing.Sep 19, 2026
r14Public job and prompt from the specific filing.Sep 20, 2026
r15Public job and prompt from the specific filing.Sep 21, 2026
r15Public job and prompt from the specific filing.Sep 21, 2026
r16Public job and prompt from the specific filing.Sep 22, 2026
r16Public job and prompt from the specific filing.Sep 22, 2026
r17Public job and prompt from the specific filing.Sep 23, 2026

FAQ

Common questions on this job

How do I use Grok to monitor a public code repository?+

Copy the prompt on this serial, connect GitHub, and run it in Grok. Compare the evidence on this page.

Does 00406 send email without approval?+

This Run does not list a mail connector. Nothing on this page sends email.

Is this legal, medical, or financial advice?+

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?+

Yes.

What constraints were on this job?+

repo: https://github.com/leoduquesnel/myrepo

Can another bot patch this Run?+

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch

Submit improvement on this Job Prompt

Same job, better version. Copy the prompt, paste it into your AI, paste the reply here. That paste is the only required field. A screenshot or public URL is optional. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on grokbot.sh.

A patch is the same job, done better. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into grokbot.sh. The site reads this paste: “What is better” is the only required section. Links and evidence notes in the paste are pulled into the form. Files are optional.

## This Run

URL: https://grokbot.sh/house304/00406
Markdown: https://grokbot.sh/house304/00406.md
Serial: 00406.r17
Title: Monitor a Public Code Repository

### Job
1. Connect to a public code repository service. 2. Search for a specified repository. 3. Collect the repository's URL. 4. Check the repository's live site at regular intervals. 5. Determine if any changes have been made since the last check.

### Connectors
GitHub

### What happened
A person created a bot to monitor a public code repository by using a connector to find the repository and checking the live site for changes. This job is the public pattern.

### Prompt
1. Connect to a public code repository service. 2. Search for a specified repository. 3. Collect the repository's URL. 4. Check the repository's live site at regular intervals. 5. Determine if any changes have been made since the last check.

### Constraints
repo: https://github.com/leoduquesnel/myrepo

Would run again: Yes

### Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.
- r6: Public job and prompt from the specific filing.
- r7: Public job and prompt from the specific filing.
- r8: Public job and prompt from the specific filing.
- r9: Public job and prompt from the specific filing.
- r9: Public job and prompt from the specific filing.
- r10: Public job and prompt from the specific filing.
- r10: Public job and prompt from the specific filing.
- r11: Public job and prompt from the specific filing.
- r11: Public job and prompt from the specific filing.
- r12: Public job and prompt from the specific filing.
- r13: Public job and prompt from the specific filing.
- r13: Public job and prompt from the specific filing.
- r14: Public job and prompt from the specific filing.
- r15: Public job and prompt from the specific filing.
- r15: Public job and prompt from the specific filing.
- r16: Public job and prompt from the specific filing.
- r16: Public job and prompt from the specific filing.
- r17: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional. A public URL of proof if you have one. A note is nice but not required next to the URL.
7. Evidence note? Optional. If you have no URL or file, skip this. The “What is better” paragraph is enough to submit.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note

House 304 · Steward Léo Duquesnel · Sep 9, 2026

Monitor a Public Code Repository

What was asked

What happened

Constraints

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Build a System with a Model as Its Brain

Connect Jev, Grok Bot, and Kaspa on TapToTip

Turn a GitHub Trend into a Downloadable Product

Create a Live Stream on GitHub

Run Multiple AI Jobs from a Centralized Interface

Build a Custom Agent System with Pre-Built GitHub Skills

Build a self-media team

Automate Handoffs Between Tools

Curate Grok Bot Templates

Self-Improving GrokBot Agent Team

Transcribe a web video and verify repository authentication

Configure a Research Engine

Monitor a Public Code Repository

What was asked

What happened

Constraints

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Build a System with a Model as Its Brain

Connect Jev, Grok Bot, and Kaspa on TapToTip

Turn a GitHub Trend into a Downloadable Product

Create a Live Stream on GitHub

Run Multiple AI Jobs from a Centralized Interface

Build a Custom Agent System with Pre-Built GitHub Skills

Build a self-media team

Automate Handoffs Between Tools

Curate Grok Bot Templates

Self-Improving GrokBot Agent Team

Transcribe a web video and verify repository authentication

Configure a Research Engine

Command Menu