菜单
Carry one human-approved myIO package issue through test-first implementation, package checks, and an unmerged PR without releasing or submitting to CRAN. Use for scheduled myIO backlog work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Research myIO package, chart-engine, MCP, CRAN, compatibility, and performance opportunities and create evidence-backed research candidates. Use for scheduled myIO scouting or inbound enhancement triage.
Run R CMD check --as-cran on the myIO package, parse the output, and map each ERROR/WARNING/NOTE to a concrete fix
Simulate a CRAN reviewer evaluating myIO for acceptance. Adversarial review that flags rejection risks before you submit.
End-to-end CRAN submission workflow for myIO — pre-checks, fix cycles, tarball build, cran-comments.md, and resubmission handling. Use when preparing to submit or resubmit to CRAN, or when you receive CRAN reviewer feedback.
Bump version (semver-computed from what's actually merged), finalize NEWS.md, run the full CRAN-readiness gate, build the tarball, tag and create the GitHub Release. Stops before the actual CRAN upload/email confirmation — that step needs the maintainer. Designed for scheduled one-time invocation.
Document and enforce R package versioning strategy for myIO. Covers semantic versioning, backward compatibility policy, deprecation schedules, and CRAN constraints. Use when planning a release, deprecating a function, or documenting versioning decisions.
| name | backlog-pipeline |
| description | Carry one human-approved myIO package issue through test-first implementation, package checks, and an unmerged PR without releasing or submitting to CRAN. Use for scheduled myIO backlog work. |
Require backlog-ready, non-red main, no open automation-pr, and an isolated worktree. Evaluate every gate against remote state, never the local checkout: run git fetch origin first, and answer any merged/landed/shipped question with git merge-base --is-ancestor <sha> origin/main or gh pr view <n> --json state reporting MERGED — a commit appearing in bare git log proves nothing about main, because an unattended run may start on an unmerged feature branch. Process one issue. Add a failing R, JavaScript, MCP, or integration contract before implementation as appropriate. Preserve myIO as the canonical engine and coordinate wrapper-visible behavior with pymyIO.
Run focused tests plus the repository's package, JavaScript, MCP, and documentation checks applicable to the change. Open one PR labeled automation-pr with provenance, Closes #N, commands/results, downstream compatibility risks, and unrun external gates. Stop before version bump, release, publication, or CRAN submission.
