All authors

Claude Skills by HsuanYuLee
github.com/HsuanYuLee17 skills0 installs22 views
- Checkpoint保存、恢復、列出長 session checkpoint;記錄 branch、ticket、todo、recent activity,方便中斷或 context compression 後接續。Votes: 0GitHub stars: 5
- EngineeringEngineer-minded execution orchestrator: takes a planned JIRA ticket and implements it with strict quality discipline — TDD, lint, typecheck, test, behavioral verify, PR. Two modes: first-cut (new implementation) and revision (fix PR review comments by returning to the work order). Local-only workflows may register delivery extensions, but those extensions are not part of the portable skill contract. Supports batch mode via parallel sub-agents. Trigger: "做 PROJ-123", "work on", "engineering", ...Votes: 0GitHub stars: 5
- LearningUse when the user wants to learn from external resources (URLs, repos, articles), extract patterns from merged PRs, process a learning queue, configure the daily learning scanner, or backfill review lessons. Trigger: '學習', 'learn', '研究', 'deep dive', '學習 PR', '每日學習', 'daily learning', '設定學習', '批次學習', '掃歷史 PR', or when user shares a URL to analyze.Votes: 0GitHub stars: 5
- Memory HygieneManual memory tiering — classify Hot/Warm/Cold, review candidates, and migrate MEMORY.md index + memory files. Use when the session-start advisory fires, MEMORY.md Hot grows past 15 entries, or you want a periodic cleanup. Trigger "memory-hygiene", "整理記憶", "memory 降級", "/memory-hygiene", "decay scan", "tier memory".Votes: 0GitHub stars: 5
- Pr PickupSlack collaboration layer: extracts PR URLs from Slack messages and dispatches to engineering revision mode. Does NOT modify code — all code changes, GitHub review replies, and lesson extraction are engineering's responsibility. Trigger: "pr-pickup", "pickup", Slack URL + PR intent ("pickup <slack_url>", "處理 <slack_url>", "同仁貼的 <slack_url>", "接這個 PR <slack_url>"). NOT for: reviewing others' PRs (use review-pr), first-cut implementation (use engineering directly), fixing your own PR without Sl...Votes: 0GitHub stars: 5
- Refinement流程的第一站,也是第一個關卡:把「怎麼算成功」談成人簽得下去的 assertion,凍結起來。由 driving-work-to-done 在判定要立案之後帶進來。 driving-work-to-done 判定一件事要立案、而現場還沒有對應的單時。 也用於:既有單的成功定義本身錯了,停 `assertion_wrong` 之後回來重簽。 不用於:判斷「這件事要不要立案」——那在 driving-work-to-done。Votes: 0GitHub stars: 5
- Review Inbox"Use when the user wants to discover and review PRs across the team awaiting their attention. NOT for a single specific PR (use review-pr). Supports three discovery modes: Label (GitHub label scan), Slack (channel-wide scan), Thread (specific Slack thread URL). Trigger: '掃 PR', 'review 大家的 PR', '批次 review', '有哪些 PR 要我看', Slack thread URL + review intent ('review <slack_url>', '幫我看這串'). Key: '我的 PR' → request-pr-review; '大家的 PR' / Slack URL → here; single PR URL → review-pr." 要掃出團隊裡等著自己看的 PR。...Votes: 0GitHub stars: 5
- Review PrReview someone else's PR as a code reviewer: read the PR diff, check against .claude/rules, leave inline comments on issues found, and submit a review with APPROVE or COMMENT (REQUEST_CHANGES only when the user says so). Use when the user asks the assistant to review a PR (subject omitted or = self), e.g.: "review PR", "review 這個 PR", "review 此 PR", "review 該 PR", "幫我 review 這個 PR" (without team subject), "review for me", "code review", or shares a PR URL with self-directed review intent. NOT...Votes: 0GitHub stars: 5
- Standup"Use when the user wants to generate a daily standup report or end-of-day summary (YDY / TDT / BOS / 口頭同步). Single entry point for all standup and end-of-day workflows. Trigger: 'standup', '站會', 'daily', '寫 standup', '下班', '收工', 'EOD', 'wrap up', '今天做了什麼'." 要產出每日站會報告或下班摘要。例如「站會」「daily」「下班」「收工」 「EOD」「今天做了什麼」。 不用於:一張單走到哪(走 driving-work-to-done)、工時補登(走該公司自己的 worklog skill)。Votes: 0GitHub stars: 5
- Verify AC施工告一段落、要判這次到底算不算達成時的站。跑硬化 oracle 給出會擋人的機械判定,另出不擋人的判斷報告,兩者分開。流程的第二個關卡,也是最後一個。 某張單做到一個段落,要驗收的時候。例如「驗收一下」「這樣算完了嗎」「跑一次判定」 「可以出貨了嗎」,或剛從 engineering 交出來。 判 PASS 之後也在這裡寫交付紀錄,供釋出尾段讀。 不用於:還在做、只是想跑個測試看看(那是 engineering 的量測)、 決定下一站是哪一站(走 driving-work-to-done)。Votes: 0GitHub stars: 5
- Visual RegressionTransitional standalone visual regression guard using before/after screenshot comparison. Two modes: SIT (compare staging vs local dev) or Local (compare git-stashed base vs current changes). No long-lived baselines — captures fresh screenshots each run and deletes after comparison. Config-driven from workspace-config.yaml. Use when: "跑 visual regression", "檢查畫面", "頁面有沒有壞", "visual test", "screenshot test", "畫面測試", "截圖比對", "有沒有跑版", "畫面壞了嗎", "UI 有沒有問題", "check if pages look right", for standal...Votes: 0GitHub stars: 5
- Check Your Own WorkBefore handing your own change over — opening a PR, asking for review, saying "done" — check it against nine questions that come from what reviewers actually caught: claims that do not match the diff, the repo's own rules not applied, half-done pattern changes, runtime behaviour asserted from reading source, last round's comments still unaddressed, assertions that cannot fail, a mechanism you removed whose jobs nobody carried over, and something you added that nothing runs or that this repo h...Votes: 0GitHub stars: 5
- Command PostCommander mode: use when one session commands the other Claude sessions on this machine — to read the map of who holds what, to dispatch work (one-to-one or a mutual review between several sessions), to watch its own stability signals, to keep the commander journal that the next commander reads, to print copy-pasteable rebuild prompts when sessions die, to hand the commander role to the next session, or to escalate a decision to the human. Reads each session's own declaration plus the local r...Votes: 0GitHub stars: 5
- Driving Work To Done把一件工作從「有人說了一句話」帶到「judged 過的交付」:先判斷要不要立案,再決定現在 該在 refinement / engineering / verify-ac 哪一站、什麼時候換站,載入說明「這類工作怎麼算 done」的知識,然後一路推進到收斂或撞上四種已宣告的停點之一。任何會改變程式碼或行為的 請求都從這裡進,使用者不需要知道這個名字。唯讀的查詢與說明不走這裡。 有人帶著一件要做的事出現時的第一站,不論他有沒有說出任何指令名稱。例如 「幫我做 X」「這個壞了要修」「想重構 Y」「繼續」「接著推」。 也用於:不知道現在在哪、不知道下一步是什麼、手上有多張單不知道先做哪一張。 不用於:唯讀的查詢與說明(「這支腳本在幹嘛」「查一下 X」)——那些沒有「怎麼算成功」 要簽,直接回答。Votes: 0GitHub stars: 5
- Framework Self Dev在框架自己身上施工時要知道的事:一張框架單怎麼開。兩種單——舉發實作途中撞到的問題、 開發框架新功能——開單那一刻問的格子不一樣,而舉發那一種要先看過還沒出去的單裡有沒有 同一件。 要改的東西是這套流程自己(skill、它們的腳本、常駐規則)的時候載入。例如「framework 單怎麼開」「開一張框架的單」「這是框架的問題」「舉發框架有問題」,或 driving-work-to-done 判定這件工作落在框架 repo 自己身上。 不用於:某一個產品 repo 的工作(那是那個 repo 自己的知識 skill)、任何一類工作的完成 條件(那是 swe-knowledge)、決定下一站是哪一站(那是 driving-work-to-done)。Votes: 0GitHub stars: 5
- Request Pr Review"把使用者名下已經開好的 PR 蒐集起來、帶回每一個的 review 狀態、列出來讓他決定要請誰看,然後通知對的人。Trigger: '我的 PR', 'request PR review', 'ask someone to review my PR', 'PR 狀態', '催 review', '催 PR', 'PR 被 approve 了嗎', '幫我掃我的 PR', '請同仁 review', '請同仁幫我 review', '請大家 review', '請大家幫我 review', '請大家幫忙看一下', '找人 review', '找誰 review', '請[人名/角色]幫我 review', '請[人名/角色]幫忙看 PR'. 主語為同仁/大家/人名/角色的「請X幫我 review」屬於催 review 範疇,不要 route 到 review-pr。" 使用者問**自己的** PR 現在怎麼樣,或想找人來看。例如「我的 PR」「PR 狀態」 「催 review」「PR 被 approve 了嗎」「請同仁幫我 review」。 「請〈某人/大家〉幫我 revie...Votes: 0GitHub stars: 5
- Swe Knowledge軟體工程這一類工作「怎麼算 done」的通識:改動住在一條 branch 上、有一個 PR、判定過才 進預設分支、push 之前本機跑完跑得動的驗證。由 driving-work-to-done 在判定一件工作會改到 程式碼時載入。很少、扁平、不含任何一家公司或一個專案特有的東西。 driving-work-to-done 判定這件工作會改到程式碼、要進版控時載入。 不用於:不會產生程式碼變更的工作(報告、調查、文件、資料分析)——那些沒有這裡的 完成條件,走 `--pack none`。 不用於:某一家公司或某一個專案特有的規則(codecov 門檻、stage 部署流程、ticket 命名)。 那些在各自的公司 pack 裡,見〈跟公司 pack 的關係〉。Votes: 0GitHub stars: 5