A walkthrough of a merge request for Nick to read instead of the diff. Trigger on "walk me through !N", "walkthrough of !N", "/nick-walkthrough <iid>" and on a pasted block that starts with "Nick's feedback on the walkthrough". It explains what the merge request does as a list of points, shows the code behind each point and opens an HTML page that Nick comments on. It never posts anything to GitLab.
NTCoding/wip-skillz
A bunch of AI skillz I'm constantly tweaking and iterating. For my pesonal use, not always upto date withy my local copy.
Repository statistics
Indexed skills
5
Skill groups
1
GitHub stars
7
Forks
0
Skills
5 totalExplain code, a problem, an idea or a decision so that the reader understands it on the first read. Use it whenever a reply explains how code works, why something happens, what a change does or what a review found. Use it whenever Nick has to decide something too. Also trigger on "/explain-clearly", "explain", "why", "how does", "what does", "walk me through", "I don't understand what you mean" and "what are you talking about?". Every explanation follows Point, Explain, Evidence (PEE). A decision ends with a list of options, their trade-offs and a recommendation.
Use before creating a merge request or pull request, or before changing the description of one (glab mr create, glab mr update, gh pr create, gh pr edit). Also use it to fix the description of an existing MR ("fix the description of !N"). Every description is approved by Nick before it is posted.
A first pass over a merge request, or a group of them, for Nick to read before he reviews. Trigger on "review !N", "review these MRs", "/nick-review <iid…>". It checks correctness against the spec, compliance with the repository's rules, and simplification. One subagent per merge request. It opens an HTML report and never posts anything to GitLab.
Rewrite a document so that it reads like Nick wrote it. Any document, like a README, an ADR, a skill, a guide, a wiki page, an MR description. Trigger on "rewrite this like me", "rewrite in my tone", "this is AI slop", "this reads like AI", or /rewrite-like-nick <path>. The whole document is never rewritten before Nick approved a calibration on a small sample.
Add to your README
The badge links readers to this page. It shows the skilld mark and no counts, and it follows the reader's light or dark GitHub theme.
<a href="https://skilld.dev/gh/ntcoding/wip-skillz">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://skilld.dev/b/ntcoding/wip-skillz?theme=dark">
<source media="(prefers-color-scheme: light)" srcset="https://skilld.dev/b/ntcoding/wip-skillz?theme=light">
<img alt="Skill repository on skilld.dev" src="https://skilld.dev/b/ntcoding/wip-skillz?theme=light">
</picture>
</a>