Menu
List notable new tools, scripts, aliases, and config changes from recent git history
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/meain/dotfiles --skill whats-newThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Create a literate org-mode document with executable bash source blocks (org-babel) so the user can re-run commands/queries themselves in Emacs, then open it via emacsclient. Triggers: /literate-org, 'literate org document', 'org file with runnable blocks', 'org doc I can execute', 'make this verifiable in org', 'create an org document with executable commands'
Manage Jira issues using the jira CLI — lookup, create, edit, transition, assign, comment, link, and search. Triggers: /jira, "look up jira issue", "check jira ticket", "create jira issue", "update jira", "move ticket to", "assign issue", "add comment to", "what's the status of PROJ-123", any mention of a Jira issue key like PROJ-123
Generate an interactive local HTML review page for a large PR or diff, grouping the changed files by logical concern (not just by file) so a reviewer can go through one theme at a time instead of a flat file list. Each concern gets its own section with a description, per-file summaries, the real diff (sliced to just the hunks relevant to that concern when a file serves more than one), and callouts for anything genuinely non-obvious. Triggers: /concern-review, "review this PR by concern", "review this large PR", "build a review dashboard", "group this diff by concern", "concern review", "help me review this PR".
Based on SOC occupation classification
| name | whats-new |
| description | List notable new tools, scripts, aliases, and config changes from recent git history |
Generate a concise list of notable new features from recent git history. Focus on things the user would actively use, not passive improvements or fixes.
git log --oneline --since="1 month ago"
If the user specifies a different time range, use that instead.
Check for new aliases that map to scripts:
git log --since="1 month ago" -p -- 'zsh/.config/zsh/aliases' 'zsh/.config/zsh/.zsh-custom/*alias*'
Look for added alias lines (lines starting with +alias) to pair with new scripts.
Only include items the user would actively invoke or benefit from knowing about. Skip:
Categorize into:
,script-name (alias))Use this exact format:
**New tools:**
- `,script-name` (`alias`) — one-line description
**Config changes worth remembering:**
- brief description of the change
Omit a section if empty. Keep descriptions to one line each.