commit-task-work

To commit task-scoped work safely across multiple git repositories, you need scoped staging that explicitly targets task-related files while ignoring unrelated dirty changes in each repo. This ensures git history stays clean and task-focused by validating branch ownership and pathspecs before committing.

Secret pattern scanning runs during the staging phase to detect and exclude sensitive data like API keys or credentials from your git commits. This validation prevents leaking secrets by checking staged diffs before the task-scoped commit is finalized across repositories.

Yes, the workflow applies multi-repo classification to handle personal_os task artifacts and external codebases simultaneously. It applies different commit rules for each repo type and asks for confirmation when branch ownership or task scope is ambiguous.

The best way to ensure only task-relevant files are staged is through explicit pathspec staging combined with task resolution from context, task folders, status files, or branch names. This scoped approach excludes caches and unrelated dirty work before running pre-commit diff checks.

Branch ownership validation matters because it prevents accidental commits to incorrect branches when managing a single task across multiple repositories. It checks branch scope and prompts for confirmation when ownership is ambiguous, keeping version control history aligned with the active task.

You should avoid scoped task commits when you intentionally want to batch unrelated changes into a single commit, or when working outside git-based version control and personal_os task workflows, as the skill relies on task artifacts and branch context to define scope.