Repository Startup Orchestrator FAQs

Question 1

What happens when I run sc-startup with the --init flag?

Accepted Answer

The --init flag launches the sc-startup-init agent which scans your repository for existing configurations, detects your package manager, and guides you through creating the required .claude/sc-startup.yaml settings.

Question 2

Can I use sc-startup without modifying my repository?

Accepted Answer

Yes, by using the --readonly flag, the skill forces all agents into a report-only mode, providing a status summary of your PRs and worktrees without applying any changes.

Question 3

Does this skill automatically commit changes to my repo?

Accepted Answer

No. While the skill can update checklists and pull branches, it is designed with safety in mind and does not perform auto-commits of checklist changes or local modifications.

Question 4

How does sc-startup handle missing agent dependencies?

Accepted Answer

It performs a pre-launch validation against your config. If a feature is enabled but the required agent is missing, it fails closed with a structured 'DEPENDENCY.MISSING' error and suggests the correct installation action.

Question 5

What is the benefit of the --fast flag?

Accepted Answer

The --fast flag skips all background agents (like PR triage and worktree scanning) and simply loads your startup prompt to quickly set the AI's role and context for the session.

Repository Startup Orchestrator

Key Features

Use Cases

Repository Startup Orchestrator

Key Features

Use Cases