Consider listing in awesome-codex-plugins
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- vim
- Domain
- documentation
Research direction
The target files are README.md and CONTRIBUTING.md in awesome-codex-plugins; start by checking the Community section and its required contribution format. Done means adding codex-vim9 in that format and opening a PR, if the curated list is useful for the project.
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:
- Fork
awesome-codex-plugins - Add an entry to the Community section in
README.mdand followCONTRIBUTING.mdfor the format - Open a PR
If the list is not useful for this project, no problem.
- Dominant language
- Vim Script
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Git-it-App/git-it-electron#1047 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
neondatabase/website#5944 ·
-
📕documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
db-ux-design-system/core-web#8239 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libsdl-org/sdlwiki#1008 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100