Emoji Cheat Sheet: All GitHub and Markdown Shortcodes in One Place

There's a specific kind of frustration that comes with asking an agent to 'add some emojis to this README'. Sometimes it uses actual Unicode emoji characters. Sometimes it uses GitHub shortcodes. Sometimes it mixes both. Sometimes it makes up codes that dont actually render. The result never quite matches what you had in mind.

The fix is to give your agent a single reference document and tell it to always use codes from that list. This cheat sheet is exactly that — a comprehensive, auto-updated table of every emoji shortcode that GitHub, Slack, and Discord support. Its maintained by ikatyang and generated automatically from the official GitHub Emoji API and the Unicode emoji list, which means it stays current without anyone having to manually update it.

Shortcodes look like :rocket: or :warning: or :heart: — wrapped in colons, no spaces. On GitHub they render inside markdown files, comments, issue descriptions, pull requests, and commit messages. Slack uses the same format for custom emoji and reactions. Discord has its own subset. The cheat sheet organizes everything by category: smileys, people, animals, food, travel, activities, objects, symbols, and flags — plus a GitHub-custom section for things like :octocat: that only work on GitHub.

1Which platforms render emoji shortcodes

GitHub renders shortcodes in: README.md and all markdown files, issue and PR descriptions, comments, commit messages, and GitHub Pages (if you're using Jekyll). Slack renders them in messages and as reaction emojis. Discord supports a large subset in messages. Plain markdown editors (like VS Code preview) usually don't render shortcodes — they need the host platform to do the substitution. So these codes are most useful when your content lives on GitHub or in Slack.

2How to tell your agent to use emoji shortcodes

The most reliable approach: paste the URL of the cheat sheet into your conversation and tell your agent which codes you want it to use going forward. You can be as specific as you want — give it a style guide like 'use :rocket: for launches, :bug: for known issues, :sparkles: for new features'. Consistent shortcodes make your project's README, changelog and commits feel polished and intentional rather than ad-hoc.

Use emoji shortcodes from https://github.com/ikatyang/emoji-cheat-sheet in all markdown files.
Conventions: :rocket: = launch/feature, :bug: = bug, :sparkles: = new, :warning: = important, :white_check_mark: = done.