Skip to main content
abhinav
GitHub-Creator-Profil

abhinav

Repository-Ansicht von 26 gesammelten Skills in 3 GitHub-Repositories.

gesammelte Skills
26
Repositories
3
aktualisiert
4. Okt. 2026
Repository-Explorer

Repositories und repräsentative Skills

prose-writing
nicht klassifiziert

Use for substantive explanations, comparisons, proposals, and multi-part answers in conversational chat; or when writing or substantially revising reader-facing prose outside the current conversation, including documentation, design documents, incident…

4. Okt. 2026
receiving-code-review
nicht klassifiziert

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.

4. Okt. 2026
recording-cli-gifs
nicht klassifiziert

Use when creating, editing, validating, rendering, or debugging local CLI and TUI demo GIFs with asciinema+agg, Betamax, or VHS, including recorder selection, scripted terminal recordings, `.tape` files, captions, keyboard overlays, waits, pacing, and…

4. Okt. 2026
writing-agent-guidance
nicht klassifiziert

Use when creating, updating, or testing agent-facing guidance, including skills, AGENTS.md, CLAUDE.md, and references linked from them; deciding when guidance should be reached or applied; repairing unclear triggers, pointers, or observed misbehavior;…

3. Okt. 2026
prose-formatting
nicht klassifiziert

Use when writing or editing prose other than ordinary conversational chat, including formatting-only edits, or when the user requests source-style prose in chat.

2. Okt. 2026
git-spice
nicht klassifiziert

Use when performing Git repository operations involving commits, amendments, fixups, branch creation or movement, stacked branches, pushes, pull request creation, metadata updates, merges, review submission, publishing, or recovery from raw Git usage.…

1. Okt. 2026
code-testing
nicht klassifiziert

Use when deciding what test evidence a code change needs, or when writing, changing, deleting, or reviewing tests or their supporting infrastructure. Do not use merely to explain an existing test result or compiler error when no code, test, or validation…

29. Sept. 2026
go-development
nicht klassifiziert

Use when writing, changing, reviewing, testing, debugging, or explaining Go code; working with Go modules, tool dependencies, or dependency source; or choosing Go language and standard-library APIs. Do not use when Go is only incidental context and no…

29. Sept. 2026
Es werden 8 von 24 gesammelten Skills angezeigt.
3 von 3 Repositories angezeigt
Alle Repositories angezeigt