chienchuanw

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

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,

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

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

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.

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

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

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 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.

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.

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".

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