Skip to content

Add Loop Engineering - #4339

Open
ChaoYue0307 wants to merge 1 commit into
sindresorhus:mainfrom
ChaoYue0307:add-loop-engineering
Open

ChaoYue0307 wants to merge 1 commit into
sindresorhus:mainfrom
ChaoYue0307:add-loop-engineering

Conversation

@ChaoYue0307

Copy link
Copy Markdown

https://github.com/ChaoYue0307/awesome-loop-engineering

Loop Engineering is the practice of designing recurring AI-agent systems that discover work, delegate to agents, verify results, persist state, decide next actions, and run again. This project maps the emerging AI/coding-agent layer above prompt, context, and harness engineering through 509 source-audited resources, operational patterns, validated contracts, runnable templates, and a structured dataset.

By submitting this pull request I confirm I've read and complied with the below requirements

Requirements for this pull request

  • This is not a fully AI-generated pull request. The repository is owner-directed and source-audited; automation is used for validation, export, and maintenance rather than a one-shot generated list.
  • This is ready for review and is not a Draft or WIP submission.
  • I read the current contribution guidelines, list-creation instructions, and pull request template multiple times.
  • I reviewed four open pull requests substantively:
  • The title is Add Loop Engineering.
  • The proposed entry describes the theme rather than the list, starts uppercase, and ends with a period.
  • The entry is at the bottom of the Computer Science category.
  • The title is title-cased and the URL ends in #readme.
  • The submission is not blockchain-related.

Requirements for the Awesome list

  • The first real commit was published on 2026-06-10, more than 30 days ago.
  • The list is human-directed and individually source-audited, not a generated link dump.
  • awesome-lint passes locally and against the public GitHub URL; the exact upstream CI script also passes.
  • The default branch is main.
  • The README includes a succinct description and a scoped definition at the top.
  • The repository reflects sustained curation work: 509 annotated resources, source-status checks, contribution/novelty/impact/evidence metadata, 15 patterns, 15 validated contracts, and 6 runnable templates.
  • The repository name is the lowercase slug awesome-loop-engineering.
  • The heading is title-cased: Awesome Loop Engineering.
  • The canonical list is a maintained Markdown file in a public GitHub repository.
  • The repository has both awesome-list and awesome topics.
  • Open issues, closed issues, open pull requests, and closed pull requests were searched; no duplicate Loop Engineering submission exists.
  • The resource list is selective, scoped to recurring AI-agent systems, and excludes unrelated meanings of loop.
  • Source status and canonical links are audited; deprecated or unsuitable material is excluded or explicitly contextualized outside the main curation.
  • The README includes a high-resolution project illustration.
  • Entries include specific, builder-oriented descriptions.
  • The Awesome badge links back to this repository.
  • The first main section is Contents, with one level of nested items at most and no Contributing or Footnotes entry.
  • The root LICENSE contains CC0-1.0 text.
  • The root CONTRIBUTING.md defines scope, quality, and formatting requirements.
  • Necessary ancillary material is kept out of the main resource flow.
  • Formatting and spelling are checked by markdownlint, awesome-lint, and repository-specific quality gates.
  • The canonical list does not use hard-wrapped prose.
  • The README does not include a CI badge.
  • The README does not use an Inspired by link at the top.

@ChaoYue0307

Copy link
Copy Markdown
Author

unicorn

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ba4d049f4f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread readme.md
- [Conversational AI](https://github.com/jyguyomarch/awesome-conversational-ai#readme) - Build awesome chatbots and digital assistants.
- [Generative AI](https://github.com/steven2358/awesome-generative-ai#readme) - Automatically generates a wide range of unique content in text, image, and audio format.
- [Position-Based Quantum Cryptography](https://github.com/Renaller/awesome-position-based-quantum-cryptography#readme) - Theory on quantum cryptography that utilizes special relativistic constraints to achieve quantum-security under certain conditions.
- [Loop Engineering](https://github.com/ChaoYue0307/awesome-loop-engineering#readme) - Designing recurring AI-agent systems that discover work, delegate to agents, verify results, persist state, and decide next actions.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Put the target list's Contents section first

For this added list, I checked the linked README and it currently introduces a ### Quick Orientation heading before ## Contents; pull_request_template.md:80-82 requires an Awesome list to have a Contents section and for it to be the first section. Until the target README moves or removes that heading, this new entry does not satisfy the repository's own submission requirements.

Useful? React with 👍 / 👎.

@ntxptrevor ntxptrevor Aug 20, 2026 •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes fix the access

@sindresorhus

Copy link
Copy Markdown
Owner

AI-generated lists are not accepted

@Luyi365

Luyi365 commented Jul 17, 2026

Copy link
Copy Markdown

Your list is excellent, but I noticed: The header image and the title are duplicated, and also The header image should link to the project website or any relevant website.

@ChaoYue0307

Copy link
Copy Markdown
Author

@Luyi365 Thank you for the concrete feedback. Addressed in ChaoYue0307/awesome-loop-engineering@1b2986e: I replaced the title-bearing banner with the standalone project mark, so it no longer duplicates the semantic H1, and linked the mark to the project website.

@Prana111025 Prana111025 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leave Review

@Alimonguno

Copy link
Copy Markdown

Good

@mxuexxmy mxuexxmy left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the entry and awesome-loop-engineering.

Entry formatting looks fine (title case, #readme, bottom of Computer Science, objective description with a trailing period).

Likely guideline issues on the list itself:

  • The README includes a GitHub Actions CI badge (actions/workflows/quality.yml/badge.svg). The Awesome list requirements say not to include a CI badge — that should be removed from the README header.
  • The main title is an HTML <h1> rather than a Markdown # Awesome Loop Engineering … heading with the Awesome badge beside it. Other compliant lists usually use the Markdown H1 + badge pattern; worth aligning so awesome-lint / human review stay happy.
  • There are many extra shields (resource counts, HF dataset, PRs welcome, license badge, etc.). Awesome lists generally keep the header minimal (illustration + Awesome badge + short description). Consider trimming the badge row.

The amount of curation work is impressive; fixing the CI badge / header pattern would make the submission closer to the official checklist.

@mxuexxmy mxuexxmy mentioned this pull request Jul 29, 2026
35 tasks done

Copy link
Copy Markdown

I reviewed the entry and the linked list. The entry itself looks correct: the title, description, URL, and placement are fine.

I found two template issues in the README. Start In 60 Seconds appears before Contents, but Contents must be the first section. The header also includes a GitHub Actions CI badge, which the template says not to include.

The PR description is out of date. It says 509 resources, 15 patterns, 15 contracts, and 6 starters, while the README now reports 974, 22, 22, and 8.

Please address these points before this can be evaluated further.

@infonality infonality mentioned this pull request Aug 20, 2026
33 tasks done
@jgsystemsconsulting

Copy link
Copy Markdown

The effort here is obvious, but the current form works against the submission:

  1. Format. The readme is ~500KB of pipe tables (~1000 resources) with only ~37 entries in the standard - [Name](url) - Description. shape, and 164 github.com links lack the #readme suffix. The guidelines expect a curated Markdown list in exactly that shape.
  2. Badges. The readme carries a CI badge (quality.yml) and a license badge — both explicitly barred (no CI badges; no license name/badge in the readme).
  3. Scale vs. curation. ~550 arXiv links reads as a survey corpus rather than "only has awesome items". Capping per section and keeping short objective blurbs would match the expected format.
  4. Self-promotion balance. Single-contributor repo whose list links its own project site, HF dataset, and starter kits ~30 times. Consider moving the kit assets out of the list surface and letting the curated third-party links carry it.
  5. Naming. "Loop engineering" is a coined term and there is already an awesome-loop-engineering under another account — differentiating the scope in the PR body would help reviewers.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants