← PR CompletionCONTENT HISTORY

Update to PR Completion

Snapshot Sep 30, 2026 · 23:13 UTC · version 0.3.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Autonomously discover task-related changes across Git repositories and submodules, run required checks, fix failures, and create compliant commits. A direct invocation normally hands off to PR creation and the full PR Completion watcher; use explicit local-only or commit-only wording to stop after commits.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 332
    }
  ],
  "name": "commit-workspace-changes",
  "skill_md_contents": "---\nname: commit-workspace-changes\ndescription: Autonomously discover task-related changes across Git repositories and submodules, run required checks, fix failures, and create compliant commits. A direct invocation normally hands off to PR creation and the full PR Completion watcher; use explicit local-only or commit-only wording to stop after commits.\n---\n\n# Commit Workspace Changes\n\nTurn intended work into validated commits in every repository that owns it. When this skill was invoked directly, continue into `$pr-completion:take-pr-to-completion` after the commit phase unless the user explicitly asked for local-only, commit-only, no-push, or no-PR work.\n\n## Invocation mode\n\nChoose the mode from the immediate caller:\n\n- **Direct lifecycle mode (default):** the user invoked this skill or asked for the commit loop without a local-only boundary. Complete the commit phase, then hand off once to `$pr-completion:take-pr-to-completion`, passing the repositories, branches, commits, validation evidence, and remaining worktree state.\n- **Phase-only child mode:** `$pr-completion:take-pr-to-completion` explicitly invoked this skill as its commit phase. Return results to the parent; never invoke the parent again.\n- **Explicit local-only mode:** the user said commit-only, local-only, no push, no PR, or equivalent. Stop after validated local commits.\n\nThis mode boundary prevents recursive skill dispatch while making a direct commit-loop request continue through PR creation and monitoring by default.\n\n## Operating contract\n\nInvocation authorizes repository discovery, ordinary checks, in-scope fixes, formatter output, explicit staging, hooks, and commits. Infer routine choices from instructions, manifests, CI, history, diffs, and task context. Ask only for a non-derivable semantic decision, unavailable required tooling, overlapping unrelated edits, or destructive action.\n\n## Discover ownership\n\n1. Snapshot the current directory, repository, branch, HEAD, staged/unstaged/untracked changes, and any active merge, rebase, cherry-pick, or revert.\n2. Discover nested repositories and registered submodules from Git metadata. Map each changed path to its owner and process deepest children before parents.\n3. Read applicable instructions for every changed repository.\n4. Separate task work from unrelated user changes. Preserve unrelated work and meaningful existing staging.\n5. Confirm each repository is on a safe branch. Escalate if a detached repository has no derivable intended branch.\n\nIf an in-scope operation has unresolved conflicts, load `$pr-completion:merge-conflict-resolution` before the normal commit loop.\n\n## Derive and run checks\n\nBuild each repository's validation contract from its instructions, hooks, manifests, package scripts, task-runner configuration, CI workflows, and contributor documentation. Run focused formatting, lint, compile/type checks, tests, and generated-file checks first, then every mandated broad check.\n\nFor each failure:\n\n1. Classify it as task-caused, pre-existing, environment/tooling, or unrelated-state interference.\n2. Fix task-caused failures narrowly; add regression coverage when warranted.\n3. Inspect formatter or generator output before accepting it.\n4. Rerun the failed check and everything invalidated by the fix.\n5. Repeat until the full validation contract passes.\n\nDo not bypass hooks, weaken tests, suppress diagnostics, invent alternate commands when canonical ones exist, or claim flakiness without evidence.\n\n## Commit safely\n\nFor each repository with intended changes:\n\n1. Re-read status and diffs. Reject conflict markers, secrets, debug output, accidental artifacts, and unrelated files.\n2. Stage explicit intended paths and inspect the staged diff.\n3. Split independent concerns when repository convention or reviewability requires it.\n4. Infer message style and scope from instructions and recent history.\n5. Use `git commit -s` when DCO is required.\n6. If a hook fails or edits files, return to validation and restage intentionally.\n7. Verify the commit and remaining worktree. Never create an empty commit.\n\nCommit child content in its owning repository. A child commit may alter the parent gitlink; commit that pointer only when parent policy makes the pin update part of this workflow.\n\n## Complete or hand off\n\nFirst report repositories, checks, fixes, commits, deliberately uncommitted changes, and blockers. Then:\n\n- In direct lifecycle mode, invoke `$pr-completion:take-pr-to-completion` exactly once and identify this work as an already-completed commit phase.\n- In phase-only child mode, return to the parent.\n- In explicit local-only mode, stop without pushing or creating a PR.\n"
}

SHA-256 of public snapshot: b19fa727c26ab68a0440cc2c64113944b7d905cea8e771c9f23824dd67304bde