Repository navigation
Add Loop Engineering - #4339
Add Loop Engineering#4339ChaoYue0307 wants to merge 1 commit into
Conversation
|
unicorn |
There was a problem hiding this comment.
💡 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".
| - [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. |
There was a problem hiding this comment.
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 👍 / 👎.
|
AI-generated lists are not accepted |
|
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. |
|
@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. |
|
Good |
mxuexxmy
left a comment
There was a problem hiding this comment.
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 soawesome-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.
|
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. |
|
The effort here is obvious, but the current form works against the submission:
|
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
Add Loop Engineering.#readme.Requirements for the Awesome list
awesome-lintpasses locally and against the public GitHub URL; the exact upstream CI script also passes.main.awesome-loop-engineering.Awesome Loop Engineering.awesome-listandawesometopics.Contents, with one level of nested items at most and noContributingorFootnotesentry.LICENSEcontains CC0-1.0 text.CONTRIBUTING.mddefines scope, quality, and formatting requirements.awesome-lint, and repository-specific quality gates.Inspired bylink at the top.