Repository navigation
Conversation
|
Thanks for making an Awesome list! 🙌 It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome. |
|
Thanks for putting this together. One concrete thing to fix before merge: the PR body still contains the template placeholder lines ( / ). I would remove those placeholders entirely so the submission reads as a clean, fully-completed awesome PR rather than a partially edited template. |
Thanks. I fixed all of these. If I missed anything please let me know. |
Thanks. I checked again and made several small mistakes. If anything is still missing I will appreciate if you can be more specific. Thanks so much! |
|
unicorn |
|
A few things worth addressing: 1. Entry description reads like a list description, not a topic description The word "tooling" puts this in the same pattern as the bad example: 2. 3. GitHub Stars badges |
|
Review of awesome-agentic-engineering Good list overall — well-organized and clearly curated. A few things worth addressing:
|
|
nice list, well organized and the categories make sense. one significant issue though:
the star badge thing is the main blocker here :) |
|
Reviewed as part of my PR (#4336). Nice, tightly-scoped list — a few substantive suggestions:
Top description is properly theme-first, and structure is clean otherwise. |
There was a problem hiding this comment.
I reviewed the catalog entry and the current linked list, ran awesome-lint (it passes), and checked all 27 GitHub repositories referenced by the README.
One list-level blocker remains: RooCodeInc/Roo-Code is currently archived, while the submission requirements explicitly exclude archived projects from the main list. Please remove it or move it to a separate archived-reference file.
The taxonomy could also be made more objective: Commercial Offering currently groups open-source Gemini CLI, Claude Code, and Codex repositories together with the closed-source Cursor product. A label such as Vendor-Specific Tools, or a split based on source availability, would tell readers what distinction the section actually represents.
https://github.com/jordimas/awesome-agentic-engineering
Agentic Engineering is the emerging discipline where AI agents autonomously plan, write, test, and evolve software under human goals. This list curates first-party docs, canonical essays, mature tools, and key papers engineering teams need to adopt agentic workflows.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request
Add Name of List. It should not contain the wordAwesome.Add SwiftAdd Software ArchitectureUpdate readme.mdAdd Awesome SwiftAdd swiftadd SwiftAdding SwiftAdded Swift- [iOS](…) - Mobile operating system for Apple phones and tablets.- [Framer](…) - Prototyping interactive UI designs.- [iOS](…) - Resources and tools for iOS development.- [Framer](…)- [Framer](…) - prototyping interactive UI designs#readme.- [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.Requirements for your Awesome list
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
awesome-linton your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.main, notmaster.Mobile operating system for Apple phones and tablets.Prototyping interactive UI designs.Resources and tools for iOS development.Awesome Framer packages and tools.If you have not put in considerable effort into your list, your pull request will be immediately closed.
awesome-name-of-list.awesome-swiftawesome-web-typographyawesome-SwiftAwesomeWebTypography# Awesome Name of List.# Awesome Swift# Awesome Web Typography# awesome-swift# AwesomeSwiftawesome-list&awesomeas GitHub topics. I encourage you to add more relevant topics.Awesome Xand a logo withAwesome X. You can put the header image in a#(Markdown header) or<h1>.Contents, notTable of Contents.ContributingorFootnotessections.https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0(replace<user>and<repo>accordingly).licenseorLICENSEin the repo root with the license text.Licencesection to the readme. GitHub already shows the license name and link to the full text at the top of the repo.unicorn.contributing.md. The casing is up to you.Contributing, positioned at the top or bottom of the main content.Footnotessection at the bottom of the readme. The section should not be present in the Table of Contents.Example:
- [AVA](…) - JavaScript test runner.Node.js, notNodeJSornode.js.You can still use a CI for linting, but the badge has no value in the readme.
Inspired by awesome-fooorInspired by the Awesome projectkinda link at the top of the readme. The Awesome badge is enough.Go to the top and read it again.