본문으로 건너뛰기
cccskills
무료GitHub에 공개

git-sync

Sync the current branch in one pass — commit the working tree as one commit per logical change (in the host repo's commit format, or the super-board writing standard), gate Supabase schema changes, merge-pull, resolve conflicts hunk by hunk, then push without force. Use when the user runs /git-sync or says "git-sync", "sync", "commit and push", "pull and push", or "sync my branch".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

EricTechPro/super-board
연동 도구Supabase
설치 방법 보기

포함된 파일(2)

  • SKILL.md4.7 KB
  • README.md1.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

/git-sync

Commit what is in the working tree, pull, push, report. One step per line. Stop and tell the user when a step says stop. NEVER force push, rebase shared history, or skip a hook (--no-verify).

1 · Look

  1. Run git status, git branch --show-current and git rev-parse --abbrev-ref @{upstream}.
  2. Run git fetch and git rev-list --left-right --count HEAD...@{upstream} for ahead/behind.
  3. Stop on a detached HEAD.
  4. Stop when a merge, rebase, cherry-pick or revert is in progress that this run did not start (.git/MERGE_HEAD, .git/rebase-merge, .git/rebase-apply, .git/CHERRY_PICK_HEAD).
  5. Nothing to commit and nothing ahead or behind: say "in sync" and stop.

2 · Commit

  1. Read the diff (git diff, git diff --staged, untracked files) and group it into logical changes. One change, one commit.
  2. Stage each group by explicit path (git add -- <path>…). NEVER git add -A, git add . or git commit -a.
  3. NEVER stage secrets: .env* (except .env.example), keys (*.pem, *.key, id_rsa*), credential or token files, or a diff line that holds a key. Stop and warn, naming the file.
  4. A file that looks like someone else's work in progress (another task's half-edit, a file you can't explain from this conversation): leave it unstaged and list it in the report.
  5. Changes already staged by the user are one group; commit them as they are.
  6. Run the Supabase gate (section 3) before any commit that touches supabase/.
  7. Commit each group. Let the hooks run; a failing hook is a stop, not a retry with --no-verify.

Commit format. The host wins.

  1. The host's AGENTS.md, CLAUDE.md or CONTRIBUTING.md defines a commit format: follow it (for example #N: type: description).
  2. Otherwise use section "1 · Commit" of the super-board writing standard (.claude/skills/super-board/references/writing-standard.md): emoji, [type], scope, subject, 1–4 bullets, Closes #N when the commit finishes a ticket.
  3. Keep any attribution trailer the session asks for.

3 · Supabase gate

Runs only when a commit group touches supabase/ (migrations, schema, functions).

  1. The supabase skill is installed: follow its "Making and Committing Schema Changes" section and skip the rest of this list.
  2. Each schema change has its own migration file named the way supabase migration new <name> names it (supabase/migrations/<timestamp>_<name>.sql). A schema edit with no migration is a stop.
  3. When the CLI and local stack are up, run supabase migration list --local.
  4. Run supabase db advisors (or the Supabase MCP get_advisors) when available.
  5. An advisor error is a stop. Warnings go in the report.
  6. CLI or stack not available: say which checks were skipped and why, then continue.

4 · Pull

  1. Run git pull --no-rebase. Merge, never rebase.
  2. No conflict: go to Push.
  3. Conflict: use the resolving-merge-conflicts skill when it is installed.
  4. Without it, resolve hunk by hunk and keep both sides' intent.
  5. NEVER use -X ours, -X theirs, git checkout --ours/--theirs on a whole file, or delete a side to make the conflict go away.
  6. A hunk whose intent is unclear: stop and ask the user, showing both sides.
  7. Run the host's fast checks before concluding the merge: typecheck, lint and tests as the host's AGENTS.md, CLAUDE.md or package.json documents them.
  8. Checks fail: fix the merge, not the checks. Still failing: stop and report.
  9. Conclude with git commit --no-edit.

5 · Push

  1. The branch has an upstream: git push.
  2. A new branch: git push -u origin <branch>.
  3. NEVER --force or --force-with-lease.
  4. The branch is the default or a protected branch (main, master, production, or the repo's default from gh repo view --json defaultBranchRef): push only after the user says yes in this conversation. Otherwise offer a branch and a PR instead.
  5. Push rejected as non-fast-forward: go back to Pull once. Rejected again: stop.

6 · Report

Keep it short:

Committed  <sha> <subject>
           <sha> <subject>
Pulled     <N> commits (<conflicts resolved: N files | no conflicts>)
Pushed     <N> commits to <remote>/<branch>
Left out   <path> — <why>
Supabase   <advisors clean | N warnings | skipped: why>

Drop the lines that do not apply.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

super-board

무료

GitHub-Project-driven autonomous pipeline. Five verbs — onboard, lint, status, run, stop — that take a Project board from empty to drained across Build → QA → Review → Done lanes (labels qa · bug · feature route each card), with graceful shutdown / resume. Use when the user says "super-board", "/super-board", "drain my GitHub project", "set up the autonomous loop", "kick off the headless build/QA pipeline", or "stop super-board".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

EricTechPro/super-board4432026년 10월 21일 업데이트

super-build

무료

Builder lane of the super-board pipeline — takes a `Ready` GitHub Project card into its own per-issue git worktree, makes the smallest safe change test-first (TDD, `ponytail` simplest-first, official docs first for third-party APIs, upgrades and auth/billing), opens a draft PR and hands it to QA and Review through the board; it never merges — merges go through the Reviewer's merge gate. Inside `super-board run` it runs as a lane agent in the in-session wave workflow (`workflows/super-board-wave.js`, no worker cap unless `max_workers` is set); standalone headless `claude -p` dispatch is legacy opt-in. Use when the user says "Super Build", "run the build loop", "/super-build", or invokes the skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

EricTechPro/super-board4432026년 10월 21일 업데이트

super-collect

무료

Find problems in one project and file them as tickets into its super-board Backlog — the board fixes them. Source plug-ins - sentry (app errors), posthog (exceptions, rage/dead clicks, failure events, web vitals, tracking gaps), github (issues not on the board), prs (recurring problems in merged PRs and their review comments), architecture (refactor findings), plus any custom source added in onboard (an MCP server, HTTP API, CLI command or app). Each candidate is checked by one fresh verifier before filing. Dry-run by default. Use when the user says "super-collect", "/super-collect", "/super-collect sentry", "collect tickets", "triage errors onto the board", "what keeps breaking", or "find refactors".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

EricTechPro/super-board4432026년 10월 21일 업데이트

super-qa

무료

Super QA canonical workflow for functional bug-bash, evidence capture, and fix-ready issue filing. Crawls routes from `docs/super-qa/queue.md` with Playwright, records screenshots/logs/HARs, files product-readable issues with clear type/priority/area labels, and continues until traversal is complete or only human-gated blockers remain. Crawling is always browser-driven, but the regression test it leaves behind is written at whichever layer the defect actually lives — unit or integration in Vitest, e2e in Playwright only when the browser is the thing that broke. Use when the user says "run super-qa", "QA review", "bug bash", "verify and fix", or invokes `/super-qa`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

EricTechPro/super-board4432026년 10월 21일 업데이트

super-review

무료

Reviewer lane of the super-board pipeline and standalone PR/branch readiness review — forms its own hypotheses before reading the builder's summary, remembers prior findings and re-checks each with file:line proof, runs an adversarial truth-check on non-trivial diffs, and classes every finding (Gap, Bug, Verification miss, Scope drift, Over-engineering via `ponytail:ponytail-review`). Merges only through `super-board-merge-gate.sh`, pinned to the reviewed head SHA, and routes other fixes to Super Build or Super QA via the board. Use when the user says "Super Review", "review this branch", "review loop", "make sure this is merge-ready", "PR review", or asks for code, architecture, security, QA evidence, or release-readiness judgment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

EricTechPro/super-board4432026년 10월 21일 업데이트

ui-refine-loop

무료

Unattended Impeccable check → fix loop on one page or component. It reads the target's code, grills Eric (at most 10 questions, "you pick" welcome) into a per-project taste and direction file, then runs bounded rounds. Each round a fresh checker runs Impeccable critique and audit (design review and detector in separate sub-agents) and ranks typed problems, and a fresh fixer chains the matching Impeccable commands (polish last), keeps checks green or reverts, and commits. Shots cover before vs now, light and dark, 1440 and 390, plus section crops. A fresh finish reviewer grades every fix, and the loop ends in a draft PR with a Before | After table. Standalone only: started by `/ui-refine-loop <route|component>`, never by the super-board lanes. Use when the user says "ui-refine-loop", "/ui-refine-loop", "refine loop", "iterate on this page", "polish this page with impeccable", or "keep polishing".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

EricTechPro/super-board4432026년 10월 21일 업데이트

EricTechPro의 스킬 모두 보기

이 스킬의 문제 신고