docs: optimize personal squad docs for git-first usage (#937)#955
Merged
bradygaster merged 1 commit intodevfrom Apr 11, 2026
Merged
docs: optimize personal squad docs for git-first usage (#937)#955bradygaster merged 1 commit intodevfrom
bradygaster merged 1 commit intodevfrom
Conversation
diberry
force-pushed
the
squad/937-optimize-personal-squad-docs
branch
from
a3c9339 to
4589f27
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Personal Squad guide to more strongly emphasize git-first workflows and backups to prevent loss of .squad/ and personal squad state.
Changes:
- Adds a prominent git/backups tip near the top of the guide.
- Expands the “Tips” section with a concrete git-first workflow and reminders about what to commit vs keep personal.
Closes #937 - Add prominent 'Git is mandatory' warning at the top highlighting data loss risks - Expand Tips section with clear git-first workflow guidance - Emphasize commits as insurance policy for team state - Add concrete examples of when state is lost without version control - Strengthen backup warnings for personal squad directory Changes focus on making the git-first requirement unmissable and actionable. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
diberry
force-pushed
the
squad/937-optimize-personal-squad-docs
branch
from
4589f27 to
227125d
Compare
Collaborator
Author
|
✅ CI passes on fork — diberry/squad PR #149 (all checks green). Copilot review feedback addressed. Ready for human review. |
tamirdresher
pushed a commit
that referenced
this pull request
Apr 21, 2026
Closes #937 - Add prominent 'Git is mandatory' warning at the top highlighting data loss risks - Expand Tips section with clear git-first workflow guidance - Emphasize commits as insurance policy for team state - Add concrete examples of when state is lost without version control - Strengthen backup warnings for personal squad directory Changes focus on making the git-first requirement unmissable and actionable. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #937
Optimizes personal squad documentation to emphasize git-first usage and prevent data loss through team state loss.
Changes
Rationale
Personal squads store accumulated team knowledge in .squad/ — decisions, skills, agent histories. Without version control, all of this is ephemeral and vulnerable. The documentation now makes git-first usage unmissable and actionable with concrete examples.
Changes are minimal and focused on the personal squad guidance file to avoid restructuring.