GitHub issue / PR / review / release bodies for Codex should run through the shared mojiemoji core before posting Japanese Markdown.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add jozobeer/mojiemoji-plugin --skill mojiemoji-github --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mojiemoji Github?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jozobeer-mojiemoji-github-mojiemoji-plugin)More formats (shields.io, HTML) on the badges page.
---
name: mojiemoji-github
description: GitHub issue / PR / review / release bodies for Codex should run through the shared mojiemoji core before posting Japanese Markdown.
---
<!-- mojiemoji-schema-version: 2.2.0 -->
# mojiemoji-github (Codex)
Use this skill when Codex is preparing Japanese GitHub Markdown for an
issue, PR, review, review reply, issue comment, or release note.
## Core First
Run the published core before posting:
```bash
uvx mojiemoji < body.md > decorated.md
```
`uvx` resolves the `mojiemoji` distribution from PyPI on first use, so no
repository checkout and no manual install are involved. Paste or pipe the
decorated output into the GitHub command. Do not hand-build stamp URLs when the
core can render them.
PR bodies need one check the core does not perform: GitHub can copy the PR body
into squash / merge commit messages, and stamps must not leak into commit
history. Before decorating a PR body, run
```bash
gh api 'repos/{owner}/{repo}' --jq '(.allow_squash_merge and .squash_merge_commit_message == "PR_BODY") or (.allow_merge_commit and .merge_commit_message == "PR_BODY")'
```
from inside the target repository, and when it prints `true`, post the PR body
undecorated — only an explicit user request overrides this. Every other surface
(issue body, review body, comment, release note) is decorated unconditionally.
## Required URL Contract
Rendered stamps must use `/emoji/<encoded-text>` and include:
- `font`
- `color`
- `animation`
- `background=transparent`
- `outline`
- `outline_width=2`
Good inline colors include `a855f7`, `22c55e`, `f59e0b`, `06b6d4`, and
`f472b6`. Good animations include `bane`, `bure`, `kirari`, `yoko_scroll`,
and `zairu`.
## Gate Behavior
Before any `gh issue`, `gh pr`, `gh release`, `gh api`, or GitHub MCP call
that posts a Japanese body, verify that the body has either already been
decorated or intentionally opts out with `<!-- mojiemoji:off -->` /
`<!-- mojiemoji:on -->`.
For PR bodies, run the repository-policy check from Core First above before
posting. When it prints `true`, do not decorate the PR body manually either,
unless the user explicitly requests decorated PR body output.
## Canonical Policies
These policies mirror the canonical skill and are not automated in this
harness, so apply them by hand:
- Color-shifting animations (`kira` / `disco` / `psycho`) must omit
`outline` and `outline_width`; a fixed-color outline fights the hue
cycle. All other animations keep the full six-parameter set.
- Skip decoration entirely for English-only bodies and for apology,
security, legal, compliance, and acceptance-criteria text.
- Keep shields.io badge rows as the first line of the body; stamps start
below them.
- prestamp output is the mechanical first pass (catalog hits only). Add
inline decoration for the remaining phrases afterwards, then show the
decorated body to the user and get confirmation before posting.
When this adapter and the canonical skill disagree, the canonical
`skills/mojiemoji-github/SKILL.md` in the plugin repository wins.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!