Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

gv

Étoiles4

Forks2

Mis à jour20 juillet 2026 à 11:39

Start a `gv --collect` review session — open the git-history-viewer in the browser so the user authors inline review comments on the current repo, then act on the feedback they finish with. Use when the user says "gv", "gv collect", "collect review", "start a review session", "let me review", "gv review", or wants to hand-author review comments in the browser for Claude to implement.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

lttr

lttr/dotfiles

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	gv
disable-model-invocation	true
description	Start a `gv --collect` review session — open the git-history-viewer in the browser so the user authors inline review comments on the current repo, then act on the feedback they finish with. Use when the user says "gv", "gv collect", "collect review", "start a review session", "let me review", "gv review", or wants to hand-author review comments in the browser for Claude to implement.
allowed-tools	Bash(gv:), Bash(vpx:)

Collect Review Comments with gv

gv --collect (the user's git-history-viewer, @lttr/gv) serves the current repo in the browser, lets the user write review comments on the diff, and on "Finish review" prints them to stdout for you to act on.

Workflow

Confirm cwd is the repo to review (else pass --repo <path>).
Launch with run_in_background: true (it blocks until Finish): gv --collect (fallback: vpx @lttr/gv --collect).
Tell the user: browser is open — add comments, then click "Finish review". Wait for the process to exit; don't poll.
On exit, comments appear between ===GV_COMMENTS_BEGIN=== / ===GV_COMMENTS_END===. Treat each as a change request, implement it, summarize per comment.

Notes

Empty block (finished with no comments) → say so and stop; don't invent work.
Pass through <file> (preselect) and --port <n> if the user mentions them.
Inverse gv --comments <file.json> only displays comments — not this skill.

Plus depuis ce dépôt

même dépôt

implement

lttr/dotfiles

Implement work from a ticket, spec, or inline description; auto-detects the next item from the task folders when no argument is given.

2026-07-214

next-steps

lttr/dotfiles

Show status overview and next steps for an .aiwork/ spec. Use when user says "next steps", "what's left", "status", "progress", or wants to see what's planned, unplanned, or incomplete for a task.

2026-07-214

skills-map

lttr/dotfiles

Scan current directory (recursively) for Claude Code skills, slash commands, agents, hooks, and plugin/MCP configs, then render an interactive HTML graph of their explicit and implicit relationships. Use when the user says "skills map", "skill graph", "visualize skills", "map skills", "how do my skills relate", or wants to audit a skill collection before publishing.

2026-07-214

to-spec

lttr/dotfiles

Turn the current conversation context into a spec. Use when user wants to create a spec (or PRD) from the current context.

2026-07-214

to-tickets

lttr/dotfiles

Break a plan, spec, or the current conversation into vertical-slice tickets, each declaring its blocking edges.

2026-07-214

aiwork-protocol

lttr/dotfiles

Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (triage, research, spec, prd, plan, review, notes, docs/). Use when the user asks to plan, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.

2026-07-214

name	gv
disable-model-invocation	true
description	Start a `gv --collect` review session — open the git-history-viewer in the browser so the user authors inline review comments on the current repo, then act on the feedback they finish with. Use when the user says "gv", "gv collect", "collect review", "start a review session", "let me review", "gv review", or wants to hand-author review comments in the browser for Claude to implement.
allowed-tools	Bash(gv:), Bash(vpx:)

Collect Review Comments with gv

Workflow

Confirm cwd is the repo to review (else pass --repo <path>).
Launch with run_in_background: true (it blocks until Finish): gv --collect (fallback: vpx @lttr/gv --collect).
Tell the user: browser is open — add comments, then click "Finish review". Wait for the process to exit; don't poll.
On exit, comments appear between ===GV_COMMENTS_BEGIN=== / ===GV_COMMENTS_END===. Treat each as a change request, implement it, summarize per comment.

Notes

Empty block (finished with no comments) → say so and stop; don't invent work.
Pass through <file> (preselect) and --port <n> if the user mentions them.
Inverse gv --comments <file.json> only displays comments — not this skill.