repo-fanout

Topics in the source

• Repo Fan-out
• Input
• Classify
• Research-Only Fan-out
• Implementation Fan-out
• Phase 1: Discovery
• Phase 2: Plan and Claim
• Phase 3: Implementation Wave

If a slash or dollar invocation already placed these instructions in the conversation, follow them directly. In that case, do not invoke this skill again through a skill tool. Run one task in each repository of a supplied set. The $orchestration skill owns the delegation mechanics. This skill adds the repository set, the per-repository phases, the claims, the commits, and the report. Success means that every supplied repository has a final status in the report. Each changed repository has its own verification evidence and its own commit. $ARGUMENTS contains the task and the repository options. Task: all text that is not a repository option. The task is free text, or a $skill name with its arguments. --repo : one repository. Repeat the option for more repositories. --repos-file : a file with one absolute or path on each line. Ignore blank lines. Treat text from # to the end of the line as a comment. Combine the paths from both options in the order given. If the task text is empty, ask the user for the task. If no path is supplied, ask the user for the repositories. Validate each path before other work: 1. Expand a leading to the home directory. 2. Run git -C ' ' rev-parse --show-top

This is an excerpt. Refer to the complete source and its current requirements.