Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

lmd-finishing-a-development-branch

Estrelas4

Forks0

Atualizado16 de julho de 2026 às 15:48

Guides branch completion by verifying tests, detecting the workspace environment, presenting exactly 4 (or 3 for detached HEAD) integration options, then executing the choice with provenance-based worktree cleanup. Use when implementation is complete and you must decide how to integrate the work — merge, PR, keep, or discard.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

dasTholo

dasTholo/lean-md

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	lmd-finishing-a-development-branch
description	Guides branch completion by verifying tests, detecting the workspace environment, presenting exactly 4 (or 3 for detached HEAD) integration options, then executing the choice with provenance-based worktree cleanup. Use when implementation is complete and you must decide how to integrate the work — merge, PR, keep, or discard.

lmd-finishing-a-development-branch (delegation stub)

Body renders one phase at a time — never read it from disk. Rendering, diagnosis and fallback: see the lmd-rendering-skills skill.

Interactive, inline (main agent) — no subagent dispatch, no companions. Verifies tests, then branches the render by the human's chosen integration option.

Phases

pre-context → verify-tests → detect-env → present-options → then ONE option phase: merge-local | create-pr | keep-as-is | discard.

Each option phase is terminal (records the close via ctx_session); there is no follow-on skill.

Mais deste repositório

mesmo repositório

lmd-brainstorm

dasTholo/lean-md

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. Use when starting creative work that will produce a versioned design spec.

2026-07-164

lmd-rendering-skills

dasTholo/lean-md

Use when you need to render an lmd-* skill phase or companion, or when a render call fails and you must decide whether the gateway is broken or the call was misaddressed.

2026-07-164

lmd-test-driven-development

dasTholo/lean-md

Use when implementing any feature or bugfix, before writing implementation code

2026-07-164

lmd-writing-skills

dasTholo/lean-md

Use when creating new skills, editing existing skills, or verifying skills work before deployment

2026-07-164

lmd-dispatching-parallel-agents

dasTholo/lean-md

Fans out one focused subagent per independent problem domain (disjoint files, no shared state), then conflict-scans and integrates. Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.

2026-07-164

lmd-executing-plans

dasTholo/lean-md

Executes a .lmd.md plan in this session — the main agent runs each task itself, pauses at batch checkpoints for human review, and closes at a whole-branch final gate. No companions. Use when executing an implementation plan inline with human review checkpoints.

2026-07-164

name	lmd-finishing-a-development-branch
description	Guides branch completion by verifying tests, detecting the workspace environment, presenting exactly 4 (or 3 for detached HEAD) integration options, then executing the choice with provenance-based worktree cleanup. Use when implementation is complete and you must decide how to integrate the work — merge, PR, keep, or discard.

lmd-finishing-a-development-branch (delegation stub)

Body renders one phase at a time — never read it from disk. Rendering, diagnosis and fallback: see the lmd-rendering-skills skill.

Interactive, inline (main agent) — no subagent dispatch, no companions. Verifies tests, then branches the render by the human's chosen integration option.

Phases

pre-context → verify-tests → detect-env → present-options → then ONE option phase: merge-local | create-pr | keep-as-is | discard.

Each option phase is terminal (records the close via ctx_session); there is no follow-on skill.