bmad-lens-postflight

Commits, pushes, and verifies clean git state across Lens session repos.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill bmad-lens-postflight-crisweber2600
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-lens-postflight
Source: https://github.com/crisweber2600/Lens.Core.Src/tree/main/_bmad/lens-work/skills/bmad-lens-postflight
Command: npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill bmad-lens-postflight-crisweber2600

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ending a Lens work session often leaves target, control, and governance repositories with uncommitted or unpushed changes, risking lost work and inconsistent repo state. This Skill enforces a mandatory closeout that commits, pushes, and verifies every touched repo is clean before the session ends. ## Core Features & Use Cases - Automated Repo Closeout: Inspects git status across the target, control, and governance repos, stages session changes, creates conventional commits, and pushes each branch. - Clean-State Verification: Re-runs git status after pushes and stops with a structured blocker if any repo remains dirty instead of reporting false success. - Safety Guardrails: Refuses to sweep unrelated user edits into closeout commits and never uses sibling git worktrees, operating only on canonical workspace checkouts. - Use Case: After finishing a Lens feature session that modified the target and governance repos, run the postflight flow to commit and push both repos and receive a verification summary with commit hashes and push status. ## Quick Start Run the lens-postflight closeout to commit, push, and verify clean state for all repos touched in this session.

Frequently Asked Questions about bmad-lens-postflight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit and push changes across multiple git repos at once?

Use the postflight closeout flow, which inspects git status in each touched repo, stages session changes, creates one conventional commit per repo, and pushes each branch. It then re-verifies every repo is clean before reporting success.

How to verify a git working tree is clean after committing?

Run git status --short after all commits and pushes complete; an empty output confirms a clean tree. This Skill performs that check on the target, control, and governance repos and stops with a blocker if any repo still shows changes.

What happens if a git push fails during session closeout?

The flow stops immediately and surfaces the exact blocking command or remote error as a structured blocker. It never reports success while a repo remains committed but unpushed.

Will the closeout commit include unrelated uncommitted changes?

No. If the working tree contains changes that cannot be safely attributed to the current session, the flow stops and asks for guidance instead of absorbing unrelated edits into the closeout commit.

Does this workflow use git worktrees for repo cleanup?

No. The flow explicitly forbids creating or using sibling git worktrees and operates only on the canonical workspace checkouts for the target, control, and governance repos.