uniclipboard
- 25 skills
- 0 followers
- 10 hours ago last updated
- ▌ Wrap · uniclipboardSession wrap-up: commit pending changes, push, write structured state for the next session to resume from. Eliminates 'glue sessions' that exist only to commit/push, and preserves debug context across sessions.
- ▌ Learn · uniclipboardRecord a lesson learned into crates/AGENTS.md (CONVENTIONS or ANTI-PATTERNS section). Use after discovering a project-specific gotcha, resolving a tricky bug, or when the user says 'remember this' about a coding pattern. Append one concise rule that will prevent the same mistake in future sessions.
- ▌ Create Pr · uniclipboardPush the current branch and open a GitHub pull request against `main`. Use when the user says "create PR", "open PR", "make a PR", "提 PR", "开 PR", "打 PR", or otherwise asks to publish their committed work for review. Before pushing it gates the diff on four things — branch name accuracy, stale `docs-site/` docs, missing PostHog telemetry, and tracing-spec conformance — and surfaces each as a candidate list for the user to approve.
- ▌ Babysit Pr · uniclipboardAutomatically monitor CI checks and review comments (coderabbitai, github-actions) on the current PR. Analyze findings, fix issues, push, and loop until all checks pass or max rounds reached.
- ▌ Design Audit · uniclipboard bundle定期审计代码库的工程设计问题（高心智复杂度、单一真相源被破坏、catch-all 胖接口、死代码、散落魔法字面量、泄漏抽象、资源生命周期靠环形缓冲）与可优化点，范围限定为自上次审计以来的 git churn，每条发现都落到 file:line 并对照本项目自己的 VISION.md / 各级 AGENTS.md / memory 规则，明确区分「意外复杂度」（要修）与「本质复杂度」（不动）。维护去重台账，重复运行只报新增。Use when 用户要做设计审计 / 每周设计复盘 / 技术债扫描，或运行 $design-audit；不用于行级 bug review（用 $review-strict）或写功能。
- ▌ React Doctor · uniclipboardUse when finishing a feature, fixing a bug, before committing React code, or when the user types `$react-doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.
- ▌
- ▌ UI Iteration · uniclipboardAgent Loop for pixel-perfect UI adjustments: extract a structured spec from the user's intent, apply changes one property at a time, self-verify via screenshot, and converge instead of ping-ponging. Designed for high-fidelity UI cloning and spacing/style iteration.
- ▌ Continue Task · uniclipboardResume work from a $wrap state file. Reads the structured active-task.json, presents a context summary, restores branch state, and lets you pick up exactly where the last session left off — no manual context rebuild.
- ▌ Gen Changelog · uniclipboard bundleGenerate bilingual, user-facing release changelogs from Git history. Use when the user asks to generate a changelog, prepare release notes, or update `docs/changelog` for a release and provides a base tag or commit.
- ▌ Plan Reviewer · uniclipboardRun an independent adversarial review loop for a Markdown implementation plan. Use when the user asks to review, validate, stress-test, or challenge a plan before implementation, including requests for a second opinion or a plan review loop.
- ▌ Pr Greenlight · uniclipboardAgent Loop that runs local pre-flight CI checks, auto-fixes issues, creates/pushes the PR, monitors CI, and loops until all checks pass. Replaces the manual chain of preflight → create-pr → babysit-pr.
- ▌ Review Strict · uniclipboard bundlePerform a strict, evidence-based review of the current branch or working-tree changes without modifying files. Use when the user asks for a strict review, deep review, senior review, merge assessment, or explicitly invokes `$review-strict`.
- ▌ Dual Side Sync · uniclipboard bundlePush the macOS working-tree changes to the Windows peer's repo via rsync over SSH. Use when the user wants to "sync to win", "push my changes to windows", "mirror the working tree", or otherwise propagate uncommitted edits from this Mac to the paired Windows machine for cross-platform testing of uniclipboard. Replaces the older SMB-mount strategy.
- ▌ Refresh Agents · uniclipboardRefresh fact-based sections of crates/AGENTS.md (STRUCTURE, WHERE TO LOOK, COMPLEXITY HOTSPOTS, KNOWN BROKEN) from current codebase state. Use after refactoring, renaming files, adding crates, or when the agent notices AGENTS.md info is stale.
- ▌ Dual Side Debug · uniclipboard bundleInspect uniclipboard logs from BOTH the macOS host and the mounted Windows peer when debugging cross-platform sync, pairing, transfer, or daemon issues. Use whenever the user asks to "check logs", "see what's happening on both sides", or describes a symptom that involves the Windows peer (e.g. "Windows didn't receive...", "Mac sent but...", pairing/transfer/sync failures during dual-side dev).
- ▌ Local Log Debug · uniclipboard bundleInspect and analyze uniclipboard's local JSONL logs on a SINGLE machine — query, filter, and time-merge the per-role (gui/daemon/cli) log files to answer "what just happened" or trace a symptom (pairing, sync, transfer, clipboard capture, daemon lifecycle) back through the logs. Use when the user asks to "check the logs", "why did X fail", "what did the daemon do", or describes a bug to diagnose from logs on this one host. NOT for cross-device peer debugging (use dual-side-debug) and NOT for writing/reviewing tracing code (use tracing-best-practices).
- ▌ E2e Test Thinker · uniclipboardAnalyze the current branch's diff against main and determine which changes are testable via CLI-based end-to-end tests. Outputs a concrete test plan with runnable test case sketches using the uc-e2e-tests harness. Use when the user wants to think about, plan, or evaluate e2e test coverage for their current work.
- ▌ IOS Log Diagnose · uniclipboard bundleDrive the UniClipboard iOS app in a simulator and read its OSLog yourself to diagnose a mobile-sync bug, instead of asking the user to paste logs. Use when debugging why the iOS sync engine or M5 reducer did something, reproducing an iOS sync / clipboard bug on the simulator, or whenever you'd otherwise ask the user "what do the logs say". All output is Swift OSLog under subsystem `app.uniclipboard` — the Rust core (uc-mobile) emits no logs of its own; the Swift shell logs the reducer's decisions.
- ▌ Error Diagnose Fix · uniclipboardAgent Loop for build/compilation errors: run the build yourself, collect ALL errors at once, find root causes via dependency analysis, fix in order, revert failed hypotheses, loop until green. Eliminates the user-paste-error → agent-guess → still-broken ping-pong.
- ▌ Systematic Debugging · uniclipboard bundleUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- ▌ Cross Device Diagnose · uniclipboardAgent Loop for cross-device sync/transfer issues: collect environment fingerprints from BOTH machines first, check memory for known patterns, manage hypotheses with forced falsification, and persist evidence via $wrap. Orchestrates dual-side-debug + local-log-debug + systematic-debugging into a structured loop.
- ▌ Tracing Best Practices · uniclipboardTRIGGER when writing, modifying, or reviewing any Rust code that involves tracing, logging, spans, events,
- ▌ Research Then Implement · uniclipboardAgent Loop for tasks that need research before implementation: check existing research first, run structured investigation (bb-browser/context7/code study), produce a Brief, then implement against the Brief. Prevents repeated research on already-studied topics and research-to-implementation drift.
- ▌ Trigger Prepare Release · uniclipboardTrigger the prepare-release workflow on GitHub Actions. Supports optional arguments for version, bump type, channel, and base branch. Defaults to bump=patch, channel=stable, base_branch=main.