docs: add AGENTS.md rules for schema branches and worktree location - #5
Merged
Merged
Conversation
Guide agents to plan schema changes on a dedicated branch separate from feature code, since all worktrees share one local Supabase stack. Also document the sibling worktree path convention in §4.
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
1 participant
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.
Summary
Adds two agent-instruction rules to
AGENTS.md(§3, §4):npm run db:types+ RLS/pgTAP tests), separate from feature code. Feature-code branches don't start until the schema branch has landed inmain. This sidesteps shared-stack schema contamination without per-worktree isolation tooling.../sous-<ticket_id>-<description>).Notes