All authors
Claude Skills by haoxiang-xu
github.com/haoxiang-xu15 skills0 installs3 views
- Gitnexus CliUse when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\"Votes: 0GitHub stars: 36
- Gitnexus Impact AnalysisUse when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\"Votes: 0GitHub stars: 36
- Release Close SprintUse when the project owner wraps or closes a PuPu version/release — \"关 0.1.10\", \"close the release\", \"版本收尾\". Verifies a Size=Release parent issue and its direct sub-issues in GitHub Project, records close evidence there, and hands it to release certification.Votes: 0GitHub stars: 36
- Release Open SprintUse when the project owner opens a new PuPu version/release — \"开 0.1.11\", \"open the next release\", \"开新版本\". Creates and scopes one Size=Release parent issue in PUPU Project; all version work is its direct sub-issues. Not for adding one item mid-release (issue-draft-ticket) or closing a release (release-close-sprint).Votes: 0GitHub stars: 36
- Community Growth AnalystAnalyze PuPu's growth, GitHub traffic, installer downloads, release performance, community and contributor health; produce a founder-facing weekly COO report or a light release-planning baseline. Use for growth analysis and reporting; route GitHub tags changes to community-repo-tags-optimization.Votes: 0GitHub stars: 36
- Community Repo Issue PollingMonitor GitHub issues, pull requests, comments and reviews; maintain a deduplicated community inbox, assess items one by one, and coordinate assignments and agreed follow-up actions. Use for repository triage, community inbox checks, or daily repo management; use release skills for release planning and delivery.Votes: 0GitHub stars: 36
- Community Repo Tags OptimizationUse when working on PuPu's GitHub topics/tags — 统计 tag 数据, 评估上次换 tag 的效果, 换/优化 tags, or when a growth report shows search-channel movement worth attributing to topics. Repo is haoxiang-xu/PuPu. Triggers: \"换 tags\", \"tag 统计\", \"优化 topics\", \"上次换 tag 有效果吗\", \"topic 数据记录\".Votes: 0GitHub stars: 36
- Community Store Verify PluginProduce version-bound PuPu security verification evidence for a selected Skill, MCP server or plugin, including code, prompt, dependency and isolated behavior checks. Use for verifying or re-verifying marketplace candidates, reviewing a verification report, or assessing badge revocation; ordinary catalog edits do not require this workflow.Votes: 0GitHub stars: 36
- Dev Ui Modal StandardStandardize modal UI to match the Settings/Tools baseline used in this repo. Use when a user asks to align modal style/spacing/typography/close-button behavior, or says a modal looks inconsistent (for example close button position, border radius, title size/font, or empty-state panel visibility).Votes: 0GitHub stars: 36
- Issue Draft TicketUse when the project owner dictates new PuPu work that should become a GitHub Project release sub-issue — during release-open-sprint or mid-release \"开个票\", \"draft a ticket for X\", \"把这个记到 board 上\". Opens a draft direction; the implementing agent may later refine the same issue.Votes: 0GitHub stars: 36
- Issue Feature AuditUse when a new PuPu feature finishes implementation and needs its consistency audit before its ticket is marked done — \"audit #123\", \"审计这个功能\", \"这个 feature 过一遍检查\" — or when release-close-sprint roll-call finds a new feature that was never audited. Also covers standalone i18n checks (\"漏翻了吗\", \"检查 i18n\"), which used to be the i18n-coverage skill.Votes: 0GitHub stars: 36
- Issue Refine TicketUse when a PuPu release sub-issue needs a researched, zero-context implementation brief — \"refine #123\" or when an implementation agent wants to expand a [DRAFT]. Optional support, not a gate: the agent implementing the ticket may refine its body directly.Votes: 0GitHub stars: 36
- Issue Start TicketRun PuPu tickets from start through user-requested close: refine, formal ticket planning, user-picked UI designs, assess weaker-model implementation and strong-model checkpoints, then implement in independent clones from dev with progress comments. Use for 开始动工、接一下、开工 with ticket URLs, formal ticket, or close for started tickets. Only on close create PRs to dev, invoke issue-feature-audit and clean up clones; version closure belongs to release-close-sprint.Votes: 0GitHub stars: 36
- Release Run PipelineOperate PuPu's protected GitHub Actions release chain when the project owner asks to build, qualify, stage, publish, resume, or inspect a release candidate. Use for exact run orchestration; do not use for release scope decisions or feature audits.Votes: 0GitHub stars: 36
- Test Evaluate Long RunEvaluate PuPu LLM long-run reports and task artifacts with Codex or Claude: reconcile harness results, assess evidenced task quality, and report gaps. Use for long-run acceptance, 长测评估, or benchmark case selection; not for launching paid runs or operating a release.Votes: 0GitHub stars: 36