SiyuQian
UserCLI toolkit for automating development workflows with Claude Code — write a plan, push to Trello, let an autonomous runner execute it
Categories
Indexed Skills (23)
devpilot-clean-code-principles
Use when writing, reviewing, or refactoring code and judging quality at the level of naming, function size, comments, error handling, class design, test quality, or code smells. Language-agnostic; defer to language-specific style skills (e.g. devpilot-google-go-style) when they conflict.
devpilot-confluence-reviewer
Review Atlassian Confluence pages and leave comments (both inline and page-level). Use this skill when the user asks to review, give feedback on, or comment on a Confluence page. Triggers on Confluence page URLs, "review this confluence page", "comment on the doc", "give feedback on the wiki page", or any mention of reviewing Confluence content.
devpilot-content-creator
SEO-optimized blog and content writing skill. Use this skill whenever the user wants to write a blog post, create content for their website, improve SEO rankings, do keyword research, or plan content strategy. Triggers on any mention of blog writing, SEO content, keyword research, content marketing, "写博客", "写文章", "内容创作", "SEO优化", or when the user wants to create any form of long-form content for a website or product. Even if the user just says "write something about X for our site", use this skill.
devpilot-google-go-style
ALWAYS use when working in a Go project — writing new Go code, modifying .go files, reviewing Go PRs, or discussing Go design decisions. Triggers on any .go file interaction, Go package design, Go naming questions, Go error handling patterns, Go test writing, or Go code review. Even if the user doesn't mention "style" or "conventions", if you're touching Go code, this skill applies.
devpilot-pm
Product manager skill for market research and feature discovery. Use when the user wants to research market needs, analyze competitors, discover user pain points, or prioritize features for a product. Triggers on /pm, "market research", "find features", "what should we build", "产品调研", "市场需求".
devpilot-pr-creator
Use when the user wants to create or update a pull request or merge request, open a PR/MR, push changes for review, update a PR description, or mark a draft as ready. Triggers on: "create pr", "open pull request", "make a pr", "submit mr", "merge request", "push for review", "ready for review", "/pr", "open mr", "ship it", "send for review", "update the pr", "update the description", "mark as ready".
devpilot-product-research
Use when the user wants to research market needs, analyze competitors, discover user pain points, or prioritize features for a product. Triggers on "market research", "find features", "what should we build", "competitor analysis", "user pain points", "产品调研", "市场需求", "竞品分析".
devpilot-trello
Interact with Trello boards, lists, and cards directly from Claude Code. Use when the user wants to view boards, search/create/move/update Trello cards, add comments, or get a board overview. Triggers on any mention of Trello, kanban boards, task cards, or project board management.
devpilot-auto-feature
End-to-end workflow for implementing OpenSpec changes with TDD and mandatory code review checkpoints between task chapters. Use instead of openspec-apply-change when the user wants quality gates, TDD, reviews between chapters, or a full implement-review-archive-sync cycle. Wraps openspec-apply-change with superpowers:test-driven-development per task, superpowers:requesting-code-review after each chapter, plus automatic openspec archival, spec syncing, and CLAUDE.md/README.md update checks. Triggers on "auto feature", "implement with tdd", "implement with reviews", "build this end to end", "implement [change] with quality gates", "full workflow", "tdd and review", or any request to implement an OpenSpec change mentioning testing, reviews, quality, or thoroughness. Also triggers when resuming a partially-completed change. If the user just says "implement [change]" without quality keywords, use openspec-apply-change instead.
devpilot-issue-triage
Use when the user wants to triage, classify, sort, or sweep open GitHub issues to decide what's worth working on — "triage these issues", "整理 backlog", "哪些可以马上修", "/triage", "sort the open issues". Sits between devpilot-scanning-repos (which files issues) and devpilot-resolve-issues (which fixes them). Read-only against GitHub — drafts comments and labels into a local report but never posts. Do NOT use for filing new issues, executing fixes, or reviewing a single PR.
devpilot-resolve-issues
Use when the user wants to resolve, fix, work through, or burn down open GitHub issues in a repository — "fix all the issues", "resolve these tickets", "work through the repo-scan issues", "clear the backlog", "fix issue
devpilot-e2e-tests
Use when the user wants to generate, scaffold, or auto-write end-to-end / browser tests for a web app — "generate e2e tests", "write Playwright tests", "auto-generate browser tests", "/e2e-tests", "test the login/checkout flow end to end". Playwright-first; drives the running app to capture real selectors and verifies each spec to green. Do NOT use for unit/integration tests, API-only tests, CLI tests, or non-Playwright e2e frameworks already present (it will stop).
devpilot-harness-engineering
Use when setting up a repository for autonomous coding agents, adding guardrails, context files, or automation so agents ship reliably without constant review. Triggers on "make this repo agent-friendly", "agents keep drifting", "set up AGENTS.md / skills / sub-agents", "harness engineering", architectural drift with agent-authored code, or retrofitting guardrails after output quality decayed.
devpilot-learn
Summarize any single article, document, or web page into a standalone HTML digest file with reader-mode styling. MUST use this skill — not raw summarization — whenever the user asks to summarize, digest, get key points from, or extract takeaways from a URL, PDF, .docx, .md, .txt, paper, report, or blog post. The skill produces a shareable HTML file you cannot generate without it. Trigger on: summarize this, key points, takeaways, digest, highlights, TL;DR, what does it say, overview, 总结, 摘要, 要点, 重点, 提取, 整理, 讲了什么. NOT for: writing new content, translating, comparing two documents, building apps, multi-source news, code review, or data/CSV analysis.
devpilot-news-digest
Fetch and summarize current news into a structured briefing across categories like International, AI, Technology, and Economics. Supports English and Chinese. ALWAYS use when the user wants current news: summaries, daily/weekly briefings, headlines, top stories, "catch me up", "what's happening", or domain-specific news (AI news, tech news, market/economics news, international affairs). Triggers on: "news summary", "news digest", "daily briefing", "weekly briefing", "what happened this week", "news roundup", "top stories", "headlines", "catch me up", "what's going on with the economy", "AI news", "今日新闻", "本周新闻", "新闻简报", "每日简报", "最近发生了什么". NOT for: building news apps, translating articles, historical data analysis, or summarizing user-provided documents.
devpilot-pr-review
Use when the user asks to review a pull request, merge request, or a diff — "review this PR", "review PR
devpilot-prompt-review
Review and improve prompts for Claude (system prompts, CLAUDE.md files, SKILL.md files, API prompts, or any LLM instruction text). Use this skill whenever the user wants to review a prompt, improve prompt quality, check prompt best practices, audit instructions for Claude, optimize a system prompt, or asks "is this prompt good?". Also trigger when the user shares a prompt and asks for feedback, or when they mention prompt engineering, prompt optimization, or prompt hygiene. Even if they just paste a prompt and say "thoughts?" — use this skill.
devpilot-scanning-repos
Use when the user asks to scan, audit, or sweep an entire GitHub repository for issues and file them as tickets — "scan this repo", "audit the codebase", "find bugs/security holes/missing tests", "check the docs are still accurate", "/repo-scan", "open issues for all the problems you find". Scans security, edge cases, testing coverage, and doc/code drift (CLAUDE.md, AGENTS.md, README.md and the docs they link to) without assuming business logic. Do NOT use for reviewing a single PR (use devpilot-pr-review) or language-specific style review (use devpilot-google-go-style).
devpilot-cv-writer
Use when the user wants to create, write, rewrite, polish, or update a CV / résumé / resume — especially for senior or staff software engineering roles. Triggers on "write my CV", "improve my resume", "rewrite this CV", "review my résumé", "update my resume", "make my CV better", "帮我写简历", "改简历", "优化简历". Produces a quantified, impact-led, one-page CV and refuses to paper over missing data with vague language.
devpilot-daily-toolkit
Personal daily-life toolkit for someone living in Auckland, NZ. Bundles four tools behind one skill: RSS news (世界科技 / AI / 世界政治 / 经济金融 / 新西兰), real-time exchange rates (any currency pair via cdn.moneyconvert.net), GitHub daily activity reports (commits / PRs / issues across the user's active repos), and NZ public holidays (Auckland-highlighted via Nager.Date). USE WHEN the user asks for any of: a personal daily / morning briefing, "my daily digest", exchange rates ("汇率", "USD to NZD", "100 AUD 换多少人民币"), NZ public holidays ("下个假期", "next NZ holiday", "Auckland anniversary day"), a daily GitHub activity report ("今日 github", "github daily report", "what did I push today"), or a blended "give me everything" briefing that combines all four. Triggers on: "daily toolkit", "my daily", "morning briefing", "今日简报", "晨报", "汇率", "exchange rate", "currency convert", "convert X to Y", "NZ holiday", "新西兰假期", "Auckland holiday", "github daily report", "今日 github", "what did I ship today". For a pure long-form general news dig
devpilot-dead-code-cleanup
Use when the user wants to find and remove dead code, unused exports, unreachable functions, or unused symbols in a Go or TypeScript repository — "clean up dead code", "remove unused functions", "find unused exports", "prune dead code", "what's unreferenced", "/dead-code". Do NOT use for unused-dependency cleanup only, formatting cleanup, or refactoring of live code.
devpilot-prd-to-issues
Use when the user wants to turn a PRD, spec, design doc, or feature brief into a set of GitHub issues — "break this PRD into tickets", "create issues from the spec", "split this into tasks", "file the work for this feature", "decompose into deliverables", "/prd-to-issues". Produces an issue tree where every ticket is a deliverable slice with explicit parent/child/blocks relationships and a bounded change size.
devpilot-resolving-review-threads
Use when responding to inline review comments after pushing fixes to a GitHub PR or GitLab MR — decide per thread whether to auto-resolve (fix verified at HEAD), reply with technical reasoning (reviewer misread or wrong), or leave open for the reviewer. Triggers on "respond to review comments", "resolve the review threads", "I pushed the fixes, now reply to the comments", "close out the review", "/resolve-review". Do NOT use for writing a review (use devpilot-pr-review) or creating a PR (use devpilot-pr-creator).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.