[User Feedback] Codex review: Use repo migration helper instead of db pull
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- postgresql, supabase
- Domain
- databases, documentation
Research direction
Open .agents/skills/supabase/SKILL.md and read the “Making and Committing Schema Changes” section. Update the guidance to account for repository migration helpers and naming conventions, while treating Supabase-generated SQL as draft content. Done means the section directs users toward the repository’s canonical migration path and filename convention.
Written by the indexing model from the issue text.
Description
What happened
Task: Generate a migration after Supabase/Postgres schema changes.
Skill said: Generate the migration with supabase db pull <descriptive-name> --local --yes.
Expected: Repos may have their own migration naming/order conventions. In this repo, migrations are created through the repo helper using the next numeric <NNN>_<slug>.sql filename, and Supabase diff/pull output should only be used as input to that repo-managed file.
Source
File: .agents/skills/supabase/SKILL.md
Section: Making and Committing Schema Changes
Fix suggestion
Add a repo-aware note: when a repository provides a migration helper or naming convention, use that helper to create the migration file. Use Supabase CLI-generated SQL as draft content only, then place it into the repo’s canonical migration path/name before review.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/agent-skills
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
supabase/agent-skills#586 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#585 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
supabase/agent-skills#583 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
supabase/agent-skills#582 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#581 ·
All issues in supabase/agent-skills
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100