Skip to content

session-flow: continue-in-background dirty-tree gate unspecified when consuming directory is not a git repository #929

Description

@kyle-sexton

Context

Found dogfooding continue-in-background (shipped in PR #924) from a session whose consuming directory is not a git repository (home directory, claude started outside any repo). The delivery step's dirty-tree gate runs git status --porcelain -uall in the consuming project and specifies behavior for clean, dirty, and linked-worktree states — but not for "not a repository at all". The command fails with fatal: not a git repository (or any of the parent directories): .git.

The sibling save-point engine (reference/save-point.md) is unaffected — memory-dir resolution has a non-repo default. Only the gate step lacks a specified branch.

Proposed work

Spec the non-repo case in plugins/session-flow/skills/continue-in-background/SKILL.md (dirty-tree gate, step 1): when the consuming directory is not a git repository, state the honest reading explicitly — there is no uncommitted work to protect and no worktree isolation to rely on; proceed with the launch and say so in the launch report. One or two sentences at the step that owns the gate, per the skill's inline-gotcha convention.

Acceptance criteria

  • Gate step names the non-repo branch and its behavior (proceed + report wording).
  • check-skill, validate-plugin-contracts, changelog-parity pass (patch bump if text ships).

References

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.priority: lowNice-to-have, cosmetic, or speculative; opportunistic.

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions