alycda
UserThis repo documents my journey learning Nix—starting from zero
Categories
Indexed Skills (3)
jj-extract-gitignores
Extract `.gitignore` changes from buried commits in a jj chain back into named in-between commits that sit right after a target ancestor (default: the project's init commit). Use when the user says "extract gitignore changes", "split off the gitignores", "roll the gitignores back to <commit>", "retroactive gitignore remediation", "/jj-extract-gitignores", or wants to land later-committed `.gitignore` additions as logical ancestors of the work that uses them. Builds a sequential chain of named in-between commits — not siblings — because siblings conflict at squash time when they all append to the same end-of-file position. Each in-between commit holds exactly one original commit's `.gitignore` delta, preserving its hunk exactly. `@` does not move. Also covers a related variant for modifying a tracked path in an ancestor commit without `jj edit` (which would let auto-tracking pollute the ancestor) — uses `jj restore --from @ --to <new>` instead of squash, with a `jj restore --from 'root()'` fix for any delete/m
jujutsu
Activates first on any git/VCS operation when Alyssa is in a Jujutsu (jj) repository — anywhere `.jj/` exists in the project tree. Use for commits, status, bookmarks, push, fetch, rebase, history rewriting, file tracking, and `.gitignore` changes. Especially trigger before creating new files, running builds, or editing `.gitignore`, since jj auto-snapshots everything and retroactive cleanup is expensive if not done right. Pinned to jj v0.43. Raw `git` commands in a non-colocated jj repo can corrupt state, so always reach for this skill first when she mentions jj, jujutsu, change IDs, revsets, bookmarks, or anything VCS-shaped in a jj repo — even if she just says "commit this" or "what's the status," because in a jj repo those words mean different operations.
html-deck
Generate self-contained, single-file HTML presentation decks — no framework, no build step, no dependencies beyond Google Fonts. Use this skill whenever the user wants to create slides, a slide deck, a talk, a presentation, or a "deck" that should be an HTML file (not PowerPoint/PPTX, not Google Slides, not a terminal/Markdown tool like presenterm). Especially use it for technical talks, conference/meetup presentations, video-series intros, or any time the user wants code-authored, version-controllable slides with a dark, editorial design. Also trigger when the user references this house style, asks for "a deck like Tonbi's", or wants to convert an outline/notes into presentable slides. Default to this skill for HTML decks even if the user doesn't say "HTML" explicitly, as long as they don't ask for PPTX or a WYSIWYG tool.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.