菜单
Pushes the current branch to both remotes (upstream corporate and origin internal) so GitHub activity appears on the user's repo. Use only when the user explicitly asks to push to both remotes, sync to both repos, or invokes this dual-remote push workflow.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/bakwankawa/lazy-code-skill --skill dual-remote-push命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
Store and retrieve conversation session context for continuity across sessions (project-level). Saves completed conversations organized by datetime (hour-level granularity) to .codex/conversations/ and enables loading previous sessions to continue context. Use when the user wants to save a conversation, load a previous session, list past conversations, or continue work from a stored session.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Enforce writing high-quality and high-performance code without unnecessary overhead. Use when generating, refactoring, or reviewing code to avoid repeated initialization, unnecessary loops, excessive memory usage, and premature optimizations, while never sacrificing code quality for speed.
正在显示 SKILL.md
| name | dual-remote-push |
| description | Pushes the current branch to both remotes (upstream corporate and origin internal) so GitHub activity appears on the user's repo. Use only when the user explicitly asks to push to both remotes, sync to both repos, or invokes this dual-remote push workflow. |
Use this skill only when the user explicitly asks to push to both remotes (e.g. "push ke keduanya", "push both", "sync ke kedua remote"). Do not run automatically on every push.
upstream = corporate (default), origin = internal.In the repo:
# Corporate repo is already the default (e.g. cloned from corporate)
git remote -v
# If "origin" points to corporate, rename it to upstream and add internal as origin:
git remote rename origin upstream
git remote add origin <URL-repo-internal-user>
If the repo was cloned from corporate and you want to keep corporate as default:
upstream → corporate repoorigin → user's internal repoEnsure default push/pull stays with corporate (e.g. git config branch.<branch>.remote upstream if needed).
main or feature/xyz).git push upstream <branch>
git push origin <branch>
main):
git push upstream <branch> && git push origin <branch>