Consider listing in awesome-codex-plugins

Open
#468 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
github, typescript
Domain
documentation

Research direction

Read the project's plugin documentation to confirm how it describes its Codex support, then check the Community section and entry format in awesome-codex-plugins's README.md and CONTRIBUTING.md. If the project fits the list, add its entry and open a PR; done means the PR follows the list's contribution format.

Written by the indexing model from the issue text.

Description

This looks like a plausible fit for awesome-codex-plugins, which is a curated list of Codex plugins.

If you want to list it, the path is straightforward:

  1. Fork awesome-codex-plugins
  2. Add an entry to the Community section in README.md and follow CONTRIBUTING.md for the format
  3. Open a PR

If the list is not useful for this project, no problem.

Dominant language
TypeScript
Stars
25.6k
Forks
2.1k
Avg merge
3h 57m
Merged PRs (30d)
170

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EveryInc/compound-engineering-plugin

All issues in EveryInc/compound-engineering-plugin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.