← all publishers

RomeoSY

@romeosy source repo

Report this profile Claim this profile

• 19 skills
• 0 followers
• 12 hours ago last updated

1. ▌
   Deep Analysis · romeosy bundle

   Structured 5-phase adversarial analysis: hidden consensus, assumption inversion, stress tests. Triggers: deep analysis, 深度分析, 战略分析, architecture review, market strategy.
   0 installs
2. ▌
   Impl Strategy · romeosy

   Decide how to implement changes before editing code. Determines the compatibility boundary: is this a released public API, an unreleased branch-local change, an internal helper, or a persisted schema? Prevents unnecessary shims and over-engineering while protecting real contracts. Use before editing runtime or API code, when the user asks about backward compatibility, migration strategy, or says: 兼容性, 怎么改, 影响范围, breaking change, implementation strategy.
   0 installs
3. ▌
   Code Simplifier · romeosy

   Simplify and refactor Python code for clarity, consistency, and maintainability while preserving functionality. Use when the user asks to simplify code, clean up code, or refactor for readability.
   0 installs
4. ▌
   Land And Deploy · romeosy

   Merge-and-deploy workflow after review approval. Verifies branch state, tests, CI/deploy readiness, and post-deploy health checks. Defaults to dry-run and only executes merge/deploy when the user explicitly requests live execution. Uses dynamic base branch and Bash/PowerShell command branches. Trigger: land and deploy, 合并发布, 上线, merge and deploy, 发布到生产.
   0 installs
5. ▌
   Document Release · romeosy

   Release documentation sync workflow. Detects shipped behavior changes, updates relevant docs, and prepares changelog/release notes drafts. Defaults to dry-run for commit/push actions, uses dynamic base branch detection, changed-files scope, and Bash/PowerShell command branches. Trigger: document release, 更新文档, release notes, changelog, 发版文档.
   0 installs
6. ▌
   Cso · romeosy

   Chief Security Officer style security review for Python-first codebases. Uses OWASP+STRIDE threat modeling, confidence-gated findings, and changed-files scope. Dynamic base branch detection and Bash/PowerShell command branches are included. Trigger: security review, cso, 安全审查, threat model, OWASP, STRIDE.
   0 installs
7. ▌
   Ship · romeosy

   Safe ship workflow with default dry-run mode. Syncs with base branch, runs tests, performs a stop-ship quick review, drafts commit and PR content, and only executes commit/push/PR when the user explicitly requests live execution. Works with or without remote repositories. Use when the user says: ship, ship it, 发布, 提交, 推上去, push, 帮我提PR, create PR.
   0 installs
8. ▌
   Guard · romeosy

   Full safety mode that combines `careful` (dangerous action gate) and `freeze` (edit boundary lock). Defaults to dry-run for risky operations, requires explicit confirmation for destructive actions, and enforces scope boundaries. Includes dynamic base branch detection and Bash/PowerShell command branches. Trigger: guard, full safety, 安全模式, 上护栏.
   0 installs
9. ▌
   Retro · romeosy

   Engineering retrospective workflow for weekly or release cycles. Summarizes delivery outcomes, defects, test health, and process bottlenecks, then outputs concrete next-week actions. Uses dynamic base branch and Bash/PowerShell command branches for evidence collection. Trigger: retro, 复盘, sprint review, weekly review.
   0 installs
10. ▌
    Canary · romeosy

    Post-deploy canary monitoring loop. Watches for runtime errors, latency regressions, and key user-flow failures over a short observation window. Defaults to read-only monitoring and dry-run rollback recommendations unless explicit execution is requested. Includes Bash/PowerShell command branches and scoped verification targets. Trigger: canary, 发布后观察, 上线监控, post deploy monitor.
    0 installs
11. ▌
    Freeze · romeosy bundle

    Edit-boundary lock for focused and safe work. Restricts write operations to a single allowed path and blocks out-of-scope edits by default. Stores lock state in `.cursor/freeze-scope.json`. Includes Bash/PowerShell instructions and dry-run behavior for out-of-scope actions. Trigger: freeze, lock scope, 限制改动范围, 只改这个目录.
    0 installs
12. ▌
    Careful · romeosy bundle

    Safety guardrail for dangerous operations. Detects destructive shell, git, database, and deployment actions, switches to dry-run by default, and requires explicit user confirmation before execution. Includes dynamic base branch detection and Bash/PowerShell branches. Trigger: careful, be careful, 危险操作, 慎重执行.
    0 installs
13. ▌
    Unfreeze · romeosy

    Remove the workspace edit-boundary lock created by `freeze`. Clears `.cursor/freeze-scope.json` and restores normal write scope. Uses safe confirmation behavior and cross-platform Bash/PowerShell command branches. Trigger: unfreeze, unlock scope, 解除限制, 取消冻结.
    0 installs
14. ▌
    Feishu MCP · romeosy

    Feishu (Lark) MCP server setup guide. Configures document-centric capabilities (docx read/write, wiki, folder, whiteboard, image, search) via the feishu-mcp and @larksuiteoapi/lark-mcp npm packages.
    0 installs
15. ▌
    Code Review · romeosy

    Pragmatic pre-merge code review for Python-first projects. Reviews only changed files, uses three severities (CRITICAL/WARNING/INFORMATIONAL), and requires confidence + evidence + mitigation checks before marking stop-ship issues. Use when user asks to review code, review a PR, check production risks, or says: code review, 代码审查, PR review, 帮我审查代码, 提交前检查. Not for readability-only refactors; use code-simplifier for that.
    0 installs
16. ▌
    Feishu Data · romeosy bundle

    Read and write Feishu spreadsheets (sheet) and bitable (multi-dimensional tables) via Feishu Open API. Use when you need to read/write sheet or bitable content, or when a Feishu document is blocked because the MCP only supports docx.
    0 installs
17. ▌
    Investigate · romeosy

    Root-cause debugging workflow for Python-first projects. Reproduce failures, build hypothesis matrix, gather runtime evidence, and only then propose minimal fixes. Uses diff-aware scope with dynamic base branch and Bash/PowerShell command branches. Trigger: investigate, debug, 排查, 根因分析, why broken, test failing.
    0 installs
18. ▌
    Plan Review · romeosy

    Structured plan review before writing code. Challenges premises, audits existing code, maps failure modes, and locks in architecture. Three modes: EXPANSION (dream big), HOLD (maximum rigor), REDUCTION (strip to essentials). Use when the user describes a feature, refactor, or design and wants a thorough review before implementation. Trigger keywords: plan review, 方案评审, 架构评审, 技术方案, review my plan.
    0 installs
19. ▌
    QA · romeosy

    Systematic QA testing using Cursor's built-in browser. Navigates pages, clicks elements, fills forms, takes screenshots, reads console errors, and produces a structured report with health scores. On feature branches, auto-analyzes the git diff to identify affected pages and test them, with fallback for repos that have no remote. Use when the user asks to QA, test my app, test this page, find bugs, smoke test, or says: qa, QA, 测试一下, 帮我测, 验收, 回归测试.
    0 installs