chienchuanw

Close out the user's day with an honest retrospective. Read today's Daily note plan, interview the user to catch work done-but-unticked, then score completion, assess every active objective's on-track status, update the tracking files (tick checkboxes, carry unfinished tasks into 延後 with reasons, refresh an objective's 目前進度 when a milestone moved), and write a review into both the Daily note and t

Create structured GitHub issues via gh CLI using type-specific templates (bug, feat, refactor, doc, perf, security). Use when filing bugs, requesting features, tracking work, opening tickets, or any intent to create a GitHub issue — even implicit phrases like "track this" or "file this".

Manually-triggered comprehensive codebase health audit covering security, architecture, documentation drift, dead code, and test coverage gaps. Produces a ranked markdown report, files prioritized GitHub issues, and proposes (but never autonomously opens) auto-fix PRs for trivial safe changes. Use when the user wants to audit, scan, review the health of, do a security check on, find dead code in,

Capture the current state of a project by updating documentation at the end of a development session. Invokes the readme skill to refresh README.md and the planning-with-files skill to record project status in a doc/ or docs/ directory. Use after merging a PR, finishing a feature, wrapping up a coding session, or any time the user wants to snapshot where the project stands — even implicit phrases

Use when the user wants to prevent broken code from being pushed, block git push when tests fail, run tests before push, set up push protection, or add a safety net against pushing untested code. Covers any request to gate pushes on test results — whether they mention "hook", "pre-push", or just describe wanting to stop bad code from reaching the remote. Also handles auto-fix/auto-repair of test f

Ingest broker / wallet screenshots and update the Obsidian portfolio tracker at Personal/Finance/Portfolio/. Reads each screenshot the user pastes (US broker, TW broker, crypto wallet/exchange), diffs the extracted holdings against existing ticker files, surfaces inferred buys/sells/transfers for user confirmation, prompts a one-line thesis-log entry for each change, then writes the transactions r

Generates a branch-vs-default comparison report with plain-language explanations and senior dev review. Use when the user asks to summarize, compare, review, or explain branch changes, or wants a PR summary before merging.

Post formatted comments on GitHub PRs or issues, approve PRs, and merge PRs via gh CLI using purpose-specific templates (feedback, question, status, approval, request-changes). Use when commenting on a PR, leaving feedback, asking a question on an issue, posting a status update, approving a pull request, merging a PR, or any intent to interact with an existing PR or issue — even implicit phrases l

End-to-end feature delivery workflow that orchestrates issue creation, branch setup, strict TDD implementation, PR opening, review-feedback handling, and session archival. Use when the user wants to ship a feature from start to finish with one command — e.g. "/feature 42", "/feature add RSS feed", "build this end-to-end", "deliver issue 17", "take this from issue to merged PR". Bundles the plan →

Generates SEO metadata (slug, subtitle, tags, title, description) for markdown articles as YAML frontmatter. Use when the user asks to add metadata, SEO info, tags, or frontmatter to an article, or wants to prepare a markdown post for publishing.

Suggests 3 commit messages based on git diff and project conventions. Use when the user asks for commit message ideas, wants help writing a commit message, or has changes ready to commit.

Push a development branch and create or update a pull request via gh CLI using type-specific templates. Optionally updates README, docs, and project tracking before opening the PR. Use after finishing development, when ready to open a PR, submit work for review, or push changes.

Plan the user's day end-to-end. Triage all five Gmail accounts (by running gmail-helper), read Google Calendar and the Objectives MOC, carry forward yesterday's unfinished tasks, classify every task on an Eisenhower matrix (urgent × important), then write a prioritized plan with time-block suggestions into the Obsidian Daily note plus a reasoning log in the Journal. Use this whenever the user want

Create a branch linked to a GitHub issue via gh issue develop, then implement the work with regular convention-following commits. Use when starting work on an issue, picking up a ticket, developing a feature branch, or any intent to begin coding against a GitHub issue.

Benchmark a skill's quality by analyzing its structure, description, documentation, and live value-add from multiple perspectives using parallel agents. Use when the user asks to benchmark, evaluate, score, audit, assess, or rate a skill's quality, or wants to know if a skill is worth keeping vs. deprecating. Also trigger when the user asks "how good is this skill", "is this skill useful", "should

Act as the user's personal email secretary across all linked Gmail accounts (work, personal, semi, lighting, foufa) via the gmail-mcp server. Triage and label today's incoming mail, auto-applying existing labels on confident matches and proposing new labels with AskUserQuestion when nothing fits; then chase the status of older threads (awaiting reply, needs action, snoozed) and write the whole pic

Read unresolved review comments on a GitHub PR, deeply evaluate each suggestion, then either fix it (via gh-dev + simplify) and push the result, or push back via gh-comment with a reasoned reply. Use when the user wants to address PR feedback, respond to reviewer comments, fix code-review suggestions, action a review, or any phrasing like "address the comments on PR #N", "respond to the review", "

Write a new README.md or improve an existing one. Use when the user asks to create, update, or improve a README, or wants to document a project and no other documentation skill is more specific.

Use when the user encountered a problem, bug, edge case, or frustration with an existing skill and wants to save that knowledge into the skill's file. Trigger phrases include "add a gotcha", "document this pitfall", "capture lessons learned", "record edge cases", "pull out what went wrong", but also trigger when the user simply describes something that went wrong or was painful with a named skill

Read-only thinking check for the Obsidian portfolio at Personal/Finance/Portfolio/. Reads every open ticker file, compares the original opening thesis against later thesis-log entries and the most recent price action, and surfaces drift (you bought for reason A but are now justifying with reason B), anchoring (you keep restating the same thesis without re-examining it), and stale theses (no new en