Mandatory for Git repository operations involving commits, amendments, fixups, branch creation or movement, stacked branches, pushes, pull request creation, pull request updates, pull request merges, review submission, publishing, or recovery from raw Git…
abhinav/home
SkillsMP has collected 9 skills from abhinav/home. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 9
- GitHub stars
- 13
- GitHub forks
- 6
Skills in this repository
Showing 9 of 9 collected skills.
Use when the user explicitly requests a Pikchr diagram, Pikchr source, a `.pikchr` file, or SVG rendered with Pikchr. Do not use for a general diagram request that does not select Pikchr as the format.
Use when drafting, revising, evaluating, reviewing, or applying a commit message; or when committing work, amending commits, creating fixup commits, creating branches as part of committing work, stacking work, inserting prerequisite work below the current…
Use when creating or updating skills, deciding when guidance should apply, testing skill behavior with subagents, repairing unclear triggers or observed misbehavior, designing pressure tests, closing loopholes, addressing rationalizations, or validating skill…
Use when creating, editing, validating, rendering, or debugging local CLI and TUI demo GIFs with asciinema+agg or VHS, including recorder selection, scripted terminal recordings, `.tape` files, Hide/Show sections, waits, sleeps, and reproducible demo…
Use when acquiring, using, inspecting, or returning temporary pooled Git worktrees with the `treehouse` CLI for isolated task work, delegated subagent work, or cleanup of leased treehouse worktree paths.
Use when creating pull requests, updating pull request branches, pushing or publishing work for review, editing pull request metadata, or submitting stacked branches. Load and follow the git-spice skill for the workflow.
Use when receiving or addressing code review feedback about changes you made, including pasted reviewer comments, inline PR comments, requested changes, review summaries, questions, nits, or direct user critique that may require replies or revisions.
Use when deciding whether a repository change needs a changelog entry, creating or updating Changie unreleased entries, choosing the correct changelog kind, or writing user-facing changelog body text in repositories that use `.changie.yaml`.