Skip to content

docs: Add Related Projects section #1010

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ArangoGutierrez wants to merge 1 commit into from
Closed

docs: Add Related Projects section #1010

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -193,6 +193,12 @@ Many thanks to these AI whisperers:
<img src="https://contrib.rocks/image?repo=f/awesome-chatgpt-prompts" />
</a>

---

## Related Projects

- [Prompts Library](https://github.com/ArangoGutierrez/promptsLibrary) — Research-backed prompt templates for Cursor IDE and Claude, featuring Chain of Verification (CoVe) and spec-first workflows

Comment on lines +196 to +201
Copy link

@coderabbitai coderabbitai bot Jan 18, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for contribution guidelines, code of conduct, and related documentation
find . -type f \( -iname "CONTRIBUTING*" -o -iname "GUIDELINES*" -o -iname "CODE_OF_CONDUCT*" -o -iname "README*" \) | head -20

Repository: f/awesome-chatgpt-prompts

Length of output: 197

🏁 Script executed:

#!/bin/bash
# Check if README mentions anything about contributions, related projects, or governance
rg -i "(contribution|guideline|related.*project|self.*promot|awesome)" README.md -A 3 -B 1

Repository: f/awesome-chatgpt-prompts

Length of output: 6075

🌐 Web query:

common guidelines criteria for adding related projects to GitHub awesome lists self-promotion policies

💡 Result:

Common, widely-used guidelines & self‑promotion rules for adding projects to GitHub “awesome” lists (summary you can reuse in a CONTRIBUTING.md):

Criteria for inclusion

  • Curated, high‑quality only (not every project). Prefer broadly useful, well‑documented projects. [1][4]
  • Actively maintained / not archived or deprecated. [4]
  • Non‑duplicate (search the list first). [3][5]
  • Project/repo must be a public GitHub repo (non‑generated README). [3]
  • Short objective description (not marketing/tagline). [3]
  • Include license and documentation links when available; prefer projects with clear usage/docs. [1][6]
  • Add one project per PR and place it in the correct category (alphabetical order). [5][3]

PR / formatting rules

  • Use the repository’s contribution template / PR title format (e.g., “Add repo-name”). [3][5]
  • Follow list’s item syntax and placement (bottom of category or alphabetical). [5]
  • Provide a single, concise description sentence ending with a period. [3]
  • Include project logo/illustration when encouraged by the list. [3]

Self‑promotion / affiliation / spam policies

  • No mass or irrelevant self‑promotion; lists are curations, not indexes. [4][3]
  • Disclose affiliation when submitting your own project (maintainers commonly require declaration). [1][6]
  • Avoid adding your own project repeatedly or across many lists; make a single, justified submission. [4]
  • One link per PR; maintainers may reject entries that read like marketing or lack merit. [5][1]

Maintenance & review practices (for list owners)

  • Require CONTRIBUTING.md / PR template and review checklist to enforce quality. [2][3]
  • Enforce rules: remove unmaintained/archive entries or move them to separate sections. [3][4]
  • Use labels/CI/linting for formatting and consistency; ask contributors to squash commits if requested. [5]

Sources/examples:

  • GitHub guidance on CONTRIBUTING & community files. [2]
  • Awesome project PR/contribution rules (examples of strict requirements). [3]
  • Sample curated awesome list contributing files and quality rules. [1][5]

If you want, I can draft a single CONTRIBUTING.md (with PR template and a short self‑promotion disclosure clause) tailored to an existing awesome repo — tell me the repo name.

🏁 Script executed:

#!/bin/bash
# Read the CONTRIBUTING.md file to check guidelines
cat -n CONTRIBUTING.md

Repository: f/awesome-chatgpt-prompts

Length of output: 2479

🏁 Script executed:

#!/bin/bash
# Search for any mention of "related projects", "self-promotion", or similar in entire repo
rg -i "(related.*project|self.*promot|contribution|guideline)" CONTRIBUTING.md -A 2

Repository: f/awesome-chatgpt-prompts

Length of output: 534

Establish criteria for "Related Projects" entries and require affiliation disclosure.

The project's CONTRIBUTING.md permits documentation improvements but doesn't specify criteria for the "Related Projects" section or require disclosure of author affiliation. The author is adding their own repository without documented guidelines or conflict-of-interest disclosure. While the formatting and content are acceptable, this creates a governance gap and sets a precedent without safeguards.

Before merging, either:

  • Add a "Related Projects" section to CONTRIBUTING.md with explicit criteria (actively maintained, relevant to ChatGPT/prompt use, non-duplicate), or
  • Require the author to disclose affiliation with the linked project and confirm maintainer approval for self-promotion
🤖 Prompt for AI Agents 
In `@README.md` around lines 196 - 201, The "Related Projects" addition lacks
contribution criteria and disclosure of affiliation; update CONTRIBUTING.md to
add a "Related Projects" policy that defines inclusion criteria (e.g., actively
maintained, directly relevant to prompts/ChatGPT use, non-duplicate, licensed
appropriately) and requires authors to disclose any affiliation/ownership and
confirm maintainer approval, or alternatively require the README "Related
Projects" entry to include an explicit affiliation disclosure line and a
maintainer-approval note; modify the CONTRIBUTING.md and/or the README "Related
Projects" entry accordingly and ensure references like "Related Projects" and
CONTRIBUTING.md are updated to reflect the new policy.

# License

This work is licensed under [CC0 1.0 Universal (Public Domain Dedication)](https://creativecommons.org/publicdomain/zero/1.0/).
Expand Down