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
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Open awesome-codex-plugins and read CONTRIBUTING.md first, then inspect README.md to find the listing format and placement. Submit a direct README.md update for codex-rules in the requested format; done means the external pull request is complete and follows that repository's contribution guidance.
Written by the indexing model from the issue text.
Description
This repo already ships .codex-plugin/plugin.json.
One repo-specific detail I checked first: PostToolUse output is context-only: it emits hookSpecificOutput.additionalContext and does not rewrite tool output.
If you want it listed, awesome-codex-plugins accepts a direct PR to README.md using the format in CONTRIBUTING.md.
If that list is not useful for this project, feel free to ignore this.
- Dominant language
- TypeScript
- Stars
- 13
- 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
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100