ReddRadar
Agent skill
conventional-commit-helper
Generate and validate Conventional Commit messages for semantic-release workflows. Use when a user asks to write a commit message, asks to commit changes, asks for commit type/scope selection, or asks to enforce Conventional Commits consistency.
Install this agent skill to your Project
npx add-skill https://github.com/shaowei-g/codex-skills/tree/main/skills/conventional-commit-helper
SKILL.md
Conventional Commit Helper
Overview
Create readable, semantic-release friendly commit messages with a consistent type(scope): subject header plus optional body and footer. Support message drafting, validation, and optional non-interactive git commit execution.
Workflow
- Inspect changes with
git status --shortandgit diff --cached --name-only. - Select
typefrom the allowed set:feat,fix,perf,revert,docs,style,refactor,test,build,ci,chore
- Infer
scopefrom the affected module, path, or subsystem. - Draft subject:
- imperative/present tense (
add,fix,update,remove) - lowercase
- no trailing period
- prefer <= 50 chars
- imperative/present tense (
- Add body text only when extra context helps review.
- Add footer lines for issue refs or breaking changes.
- Validate message using
scripts/validate_commit_message.sh. - If requested, commit with non-interactive git commands only.
Message Template
<type>(<scope>): <subject>
[optional body]
[optional footer]
## Breaking Change Rules
Use either:
- `type(scope)!: subject`
- `BREAKING CHANGE:` footer
## Resources
- Detailed guidance and examples: `references/commit-conventions.md`
- Message validator: `scripts/validate_commit_message.sh`
## Commands
Validate a message string:
```bash
./scripts/validate_commit_message.sh --message "fix(auth): reject expired refresh token"
Validate a message file:
./scripts/validate_commit_message.sh --file .git/COMMIT_EDITMSG
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
shaowei-g/codex-skills
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
shaowei-g/codex-skills
ekoen-frontend-code-review
Production-grade code review for the eKoEN frontend codebase. Use when asked to review, audit, inspect, or harden eKoEN React/Next.js frontend code, pages, components, hooks, API clients, or state layers for bugs, performance bottlenecks, TypeScript safety issues, request inefficiency, state-management risks, memory leaks, rendering regressions, error-handling gaps, duplication, or maintainability problems, especially when a structured severity-ranked report with code locations, root causes, suggested fixes, and example refactors is required.
shaowei-g/codex-skills
ekoen-backend.doc.route-error
Add HttpErrorRes responses to eKoEN backend routes when controllers can throw errors from app/util/errors/index.ts
shaowei-g/codex-skills
codex-cli-subagent-transport
Use only when native subagent execution is unavailable and the caller needs one deterministic Codex CLI run with repo-local artifacts and a manifest-based result contract.
shaowei-g/codex-skills
skill-usage-logger
All skill MUST use this logger to record usage events in NDJSON format.Log Codex skill usage events to NDJSON with safe concurrent appends.
shaowei-g/codex-skills
nodejs-package-json
Patch a Node.js project's package.json for standard build automation. Use when asked to add/standardize package.json scripts like prebuild/postbuild for TypeScript builds (rimraf dist + tsc-alias), adjust prebuild for Next.js (rimraf dist .next), or ensure an existing package.json pkg config includes required scripts/assets/targets/outputPath.
Didn't find tool you were looking for?