Ad Review
CorridorTech/PoseCap
Two-axis fresh-context code review per WORKFLOW §10. An agent skill from CorridorTech/PoseCap.
已有功能的需求变更闭环（门禁式七步）。触发硬条件：要改的功能已经实现并跑起来了。当用户说"改需求""需求变更""调整交互""改功能""重构流程"，或改动容易散到多个文件、碰到鉴权/存储/配置/权限、需要可靠验证 + 回滚方案时使用。流程：锁 scope 写 change brief → 从代码确认当前行为（不靠记忆和假设）→ 影响面与风险评估 + 回滚计划 →…
Install Req Change Workflow
$ npx skills add yunshu0909/yunshu_skillshub --skill req-change-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yunshu0909/yunshu_skillshub req-change-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coding/req-change-workflow .claude/skills/req-change-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "req-change-workflow" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/req-change-workflow into .claude/skills/req-change-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-change-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/req-change-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yunshu0909/yunshu_skillshub --skill req-change-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yunshu0909/yunshu_skillshub req-change-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/coding/req-change-workflow .agents/skills/req-change-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "req-change-workflow" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/req-change-workflow into .agents/skills/req-change-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-change-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yunshu0909/yunshu_skillshub --skill req-change-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yunshu0909/yunshu_skillshub req-change-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/coding/req-change-workflow .cursor/skills/req-change-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "req-change-workflow" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/req-change-workflow into .cursor/skills/req-change-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-change-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yunshu0909/yunshu_skillshub.git --path coding/req-change-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yunshu0909/yunshu_skillshub --skill req-change-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yunshu0909/yunshu_skillshub req-change-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/coding/req-change-workflow .gemini/skills/req-change-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "req-change-workflow" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/req-change-workflow into .gemini/skills/req-change-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-change-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yunshu0909/yunshu_skillshub req-change-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yunshu0909/yunshu_skillshub --skill req-change-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .github/skills && cp -r skills-src/coding/req-change-workflow .github/skills/req-change-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "req-change-workflow" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/req-change-workflow into .github/skills/req-change-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-change-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yunshu0909/yunshu_skillshub --skill req-change-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yunshu0909/yunshu_skillshub req-change-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/coding/req-change-workflow .opencode/skills/req-change-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "req-change-workflow" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/req-change-workflow into .opencode/skills/req-change-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-change-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
req-change-workflow- GitHub stars
- 767
- Token cost
- ~1.4k tokens
- SKILL.md length
- 619 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
已有功能的需求变更闭环（门禁式七步）。触发硬条件：要改的功能已经实现并跑起来了。当用户说"改需求""需求变更""调整交互""改功能""重构流程"，或改动容易散到多个文件、碰到鉴权/存储/配置/权限、需要可靠验证 + 回滚方案时使用。流程：锁 scope 写 change brief → 从代码确认当前行为（不靠记忆和假设）→ 影响面与风险评估 + 回滚计划 →…
- Works in 8 steps: Set the plan (optional but recommended) → Clarify the change (lock scope first) → Confirm current behavior from code… → …
- Tasks that involve PRD writing
- SKILL.md covers Overview, Workflow (gated loop) and Resources
- Runs Shell scripts from its folder
What it does
Req Change Workflow is an agent skill from yunshu0909/yunshu_skillshub. 已有功能的需求变更闭环（门禁式七步）。触发硬条件：要改的功能已经实现并跑起来了。当用户说"改需求""需求变更""调整交互""改功能""重构流程"，或改动容易散到多个文件、碰到鉴权/存储/配置/权限、需要可靠验证 + 回滚方案时使用。流程：锁 scope 写 change brief → 从代码确认当前行为（不靠记忆和假设）→ 影响面与风险评估 + 回滚计划 → 提出新设计等用户批准（未获批准绝不动代码）→ 小而局部的 diff → 跑固定回归清单 → 更新文档和决策日志。产出：change brief + 代码 diff + 回归记录 + decision log。不适用于：全新功能从零做（走 issue-pool → page-solution-design（有界面时）→ backend-logic-design（有规则需讨论时）→ prd-test-writer）、只改视觉样式不动任何逻辑（按已有界面直接调整）、新想法还没定要不要做（先用 issue-pool 入池）、写 PRD/测试用例（用 prd-test-writer）、提交推送发版（用 git-push）。注意：本 skill 的七步流程通用于任何项目，但…
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/change-brief-template.md`, `references/chrome-extension-regression-example.md` and `references/decision-log-template.md`).
It sits in Product & Project Management, covering PRD writing, Architecture decision records and Browser extensions. It works with Chrome Extensions and Git. The repository describes itself as: 云舒精选的 Claude Code Skills 集合，提升开发和产品管理效率. The licence is MIT.
When your agent uses it
- Tasks that involve PRD writing
- Tasks that involve Architecture decision records
- Tasks that involve Browser extensions
Example prompts
- “/req-change-workflow”
Requirements
- A Bash shell
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit da0d31f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Req Change Workflow loads about 1.4k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 171 tokens; SKILL.md has 619 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from yunshu0909/yunshu_skillshub at commit da0d31f, republished under its MIT licence (© yunshu0909). 619 words, ~1,413 tokens.
Download SKILL.mdSave it as
.claude/skills/req-change-workflow/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- req-change-workflow
- description
- 已有功能的需求变更闭环（门禁式七步）。触发硬条件：要改的功能已经实现并跑起来了。当用户说"改需求""需求变更""调整交互""改功能""重构流程"，或改动容易散到多个文件、碰到鉴权/存储/配置/权限、需要可靠验证 + 回滚方案时使用。流程：锁 scope 写 change brief → 从代码确认当前行为（不靠记忆和假设）→ 影响面与风险评估 + 回滚计划 → 提出新设计等用户批准（**未获批准绝不动代码**）→ 小而局部的 diff → 跑固定回归清单 → 更新文档和决策日志。产出：change brief + 代码 diff + 回归记录 + decision log。不适用于：全新功能从零做（走 issue-pool → page-solution-design（有界面时）→ backend-logic-design（有规则需讨论时）→ prd-test-writer）、只改视觉样式不动任何逻辑（按已有界面直接调整）、新想法还没定要不要做（先用 issue-pool 入池）、写 PRD/测试用例（用 prd-test-writer）、提交推送发版（用 git-push）。注意：本 skill 的七步流程通用于任何项目，但 scripts/impact_scan.sh 与 references/chrome-extension-regression-example.md 是 Chrome 扩展示例；通用回归使用 references/regression-checklist.md，按项目实际选择检查。
- metadata.status
- active
- metadata.status_updated_at
- 2026-10-06
Req Change Workflow
Overview
Use a lightweight, repeatable workflow to modify an existing requirement without scope creep or “边改边炸”. Produce clear artifacts at each gate so the user can approve before the implementation starts.
Workflow (gated loop)
Follow the steps in order. Do not implement code changes until the user approves Step 4.
Step 0: Set the plan (optional but recommended)
- Use
update_planto create 5–7 short steps: clarify → baseline → impact → design → implement → validate → document. - Keep exactly one step
in_progressat a time and advance as you finish.
Step 1: Clarify the change (lock scope first)
Ask the user for the minimal inputs, then rewrite them into a clear “change brief”:
- Target (1 sentence): what outcome changes.
- Out of scope (1 sentence): explicitly what must NOT change.
- Acceptance criteria (3–6 bullets): observable behaviors that can be verified.
- “Must keep” constraints: compatibility, performance, security, no new dependencies, no network, etc.
- Rollback expectation: can we revert by reverting a diff, or does it require data migration/backfill?
Use the template in references/change-brief-template.md.
Step 2: Confirm current behavior from code (baseline)
Do not trust memory or assumptions. Locate the real entrypoints + current data flow and summarize it in 5–10 lines:
- UI entrypoints (e.g.,
sidepanel/,options/) and where user actions are wired. - Background orchestration (e.g.,
service_worker.js). - Core modules (e.g.,
src/core/...) and storage (src/core/local/...). - Config/permissions changes (e.g.,
manifest.json).
For Chrome extension projects, scripts/impact_scan.sh can help locate likely files. For other projects, use their actual entrypoints and search tools. Then read the relevant implementation to confirm behavior.
Output artifact: “Current behavior summary” + a short file list (with why each file matters).
Step 3: Impact + risk assessment (change budget)
Before proposing a new design, list:
- Files/modules that must change and why.
- Risks: auth/session, storage migration, concurrency, caching, permission scopes, UX regressions.
- Testing checkpoints: what to verify manually (use
references/regression-checklist.md). - Rollback plan: what is safe to revert; what needs cleanup.
If changes touch manifest.json or service_worker.js, require a manual reload step in the validation plan (Chrome extensions cache aggressively).
Output artifact: “Impact & risk list” + “Rollback plan (1–3 bullets)”.
Show full SKILL.md (280 more words)Show less
Step 4: Propose the new design (get approval)
Describe the new behavior using:
- New flow (bullet sequence) including edge cases.
- State model: key states, transitions, and failure recovery.
- Change boundaries: what stays unchanged.
- Observability: logs/events/UI hints for debugging.
Then ask the user to approve:
- The acceptance criteria (Step 1) as final.
- The file list (Step 2/3) as the change budget.
- The proposed design (this step).
Do not start editing code until the user says “同意/OK/按这个做”.
Step 5: Implement with minimal, localized diffs
Implementation rules:
- Prefer root-cause fixes over patches, but keep diffs small and focused.
- Avoid scattering logic across multiple entrypoints; centralize in one module when possible.
- Keep ES module imports explicit; avoid implicit globals.
- Add short JSDoc for exported functions when introducing new exports.
- User-visible logs: actionable Chinese messages (explain what to do next).
If the change involves async flows/cross-module calls/fallbacks, add Chinese comments explaining assumptions and failure handling.
Step 6: Validate (fixed regression loop)
- Select automated and manual checks from
references/regression-checklist.mdbased on the actual project and change. Record the commands and observed results. Chrome extension examples are inreferences/chrome-extension-regression-example.md. - If
manifest.jsonorservice_worker.jschanged: reload the extension before retesting. - Record what you tested and the observed outcome (even if it is manual).
Step 7: Maintain (docs + decision log)
- Update project docs or inline notes for future maintainers.
- Add a short “Decision log” entry: why this design, what alternatives were rejected, and how to roll back.
Use the template in references/decision-log-template.md.
Resources
scripts/
scripts/impact_scan.sh: fast file candidate scan viargfor keywords + common extension entrypoints.
references/
references/change-brief-template.md: input template to lock scope + acceptance criteria.references/regression-checklist.md: project-neutral regression checklist.references/chrome-extension-regression-example.md: optional Chrome extension example.references/decision-log-template.md: lightweight decision record template.
© yunshu0909, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (scripts, references) in coding/req-change-workflow of yunshu0909/yunshu_skillshub.
- SKILL.md
- references/change-brief-template.md
- references/chrome-extension-regression-example.md
- references/decision-log-template.md
- references/regression-checklist.md
- scripts/impact_scan.sh
Open the folder on GitHubat commit da0d31f
Compare with similar skills
Req Change Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Req Change Workflow this skillyunshu0909/yunshu_skillshub | 767 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ad ReviewCorridorTech/PoseCap | 224 | — | ~2.4k | Automated safety check: Notes | Apache-2.0 | |
| Req Change Workflowaiskillstore/marketplace | 430 | — | ~1.3k | Automated safety check: Pass | None | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Knockoff Release ShipperShpigford/chops | 1.9k | — | ~1.2k | Automated safety check: Notes | Custom licence | |
| ReleaseShpigford/knockoff | 2k | — | ~2.1k | Automated safety check: Notes | Custom licence |
Similar skills
Req Change Workflow
aiskillstore/marketplace
Standardize requirement/feature changes in an existing codebase (especially Chrome extensions) by turning "改需求/需求变更/调整交互/改功能/重构流程" into a repeatable loop: clarify acceptance criteria, confirm…
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Knockoff Release Shipper
Shpigford/chops
Cuts a new Knockoff release by bumping the version, rolling release notes, tagging and shipping to the Chrome, Firefox and Apple stores with a per-store report.
Release
Shpigford/knockoff
Cut a new Knockoff release — bump the version, roll release notes, tag, and ship to the Chrome Web Store, Firefox Add-ons (AMO), and the Mac & iOS App Store, reporting per-store status at the end.
Ad Archive
alexandremendoncaalvaro/CorridorKey-Runtime
Sweep completed plan files (tasks Status:done, specs Status:shipped, PRDs Status:superseded, ADRs Status:superseded or deprecated) out of the working tree and into git history via git rm.
More from yunshu0909/yunshu_skillshub
All 25 skills in this repoDual Agent Collaboration
yunshu0909/yunshu_skillshub
让 Codex 与 Claude Code 通过本机 CLI 组成“主执行者 + 独立审查者”的对称协作闭环。用于用户要求两个模型一起完成、交叉校核、独立审查、修到 ACK，或任务涉及产品需求收敛、复杂方案、跨模块开发、迁移、安全、重要重构和高质量交付时；无论从 Codex 还是 Claude Code 启动，都由当前模型主持，并完整调用另一方完成需求挑战、方案门禁、实现冷审和最终验收。
Image Assistant
yunshu0909/yunshu_skillshub
配图助手 - 把文章/模块内容转成统一风格、少字高可读的 16:9 信息图提示词；先定“需要几张图+每张讲什么”，再压缩文案与隐喻，最后输出可直接复制的生图提示词并迭代。
Page Solution Design
yunshu0909/yunshu_skillshub
和用户一起敲定一个前端页面的整页方案（三层法：先定这页给用户什么，再定含哪几样怎么排，最后才是长什么样），最后打成一个定稿包（含高保真全状态与交互流程图）交给开发。触发：用户对一个页面说「想重做 / 重新设计 / 整页不对 / 太满 / 说不清具体改哪」，或「我们讨论一下这页怎么设计」。覆盖三种情形：① 已有页面整页重做；②「替换」——新方案占用同一个入口（同一路由 /…
Backend Logic Design
yunshu0909/yunshu_skillshub
和用户一起把一个功能「看不见的部分」敲定：数据存哪、谁写谁读、怎么加载、怎么保存、默认值和升级、核心执行规则、出问题时怎么办、旧东西怎么迁。每条规则带编号、案例和状态（已定 / 方案里有但你没拍板 / 待你定 / AI 定），用户只回答带案例的新选择题、过目没拍过板的规则；给用户看的是按「你会问的问题」分组的问答卡片（最绕的逻辑配可点的模拟器）；最后请另一家模型只读查边界，问题闭环后封成后端逻辑…
Article Study
yunshu0909/yunshu_skillshub
带用户精读一篇文章/文档并真正学透（不是出摘要）。五步：抽干货 → 切讲次 → 每讲跑「学-考-讲」循环 → 对号入座 → 实操+测验+讲错题+蒸馏。每讲产出 HTML 课件 + 笔记落盘；讲完必考一次，用户复述后必须挑不精确处拧紧；抽象概念上可交互演示（能点能跑）；全程用用户自己的业务场景当案例；学完出多题型自动判分测验卷，最后把收获蒸馏回用户的工具。核心触发条件是用户要的是"学会"而不是"要…
Issue Pool
yunshu0909/yunshu_skillshub
Issue 池全生命周期管理（开发范式 v1 规划段）。核心是一条 issue 驱动的流程：用户随手丢想法，你把糊的 issue 变成能开工的 task——产出的是“问题定义”，不是“解决方案实现”；载体就是仓库根的 ISSUES.md。五个动作：记、并、拆、转、pending。规划规模只区分 single-task（一个版本能交付）与 roadmap（需要多批滚动），不得使用…
Related
Works with
Categories
Questions about Req Change Workflow
What does Req Change Workflow do?
已有功能的需求变更闭环（门禁式七步）。触发硬条件：要改的功能已经实现并跑起来了。当用户说"改需求""需求变更""调整交互""改功能""重构流程"，或改动容易散到多个文件、碰到鉴权/存储/配置/权限、需要可靠验证 + 回滚方案时使用。流程：锁 scope 写 change brief → 从代码确认当前行为（不靠记忆和假设）→ 影响面与风险评估 + 回滚计划 →…. Req Change Workflow is an agent skill from yunshu0909/yunshu_skillshub.
When should I use Req Change Workflow?
Req Change Workflow fits situations like: tasks that involve PRD writing; tasks that involve Architecture decision records; tasks that involve Browser extensions.
How do I install Req Change Workflow in Claude Code?
Run `npx skills add yunshu0909/yunshu_skillshub --skill req-change-workflow -a claude-code`. Or copy the skill folder (coding/req-change-workflow in yunshu0909/yunshu_skillshub) into .claude/skills/req-change-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Req Change Workflow in Codex?
Run `npx skills add yunshu0909/yunshu_skillshub --skill req-change-workflow -a codex`. Or copy the skill folder (coding/req-change-workflow in yunshu0909/yunshu_skillshub) into .agents/skills/req-change-workflow in your project. Codex loads it when a task matches its description.
Can I use Req Change Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yunshu0909/yunshu_skillshub --skill req-change-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/req-change-workflow, .gemini/skills/req-change-workflow, .github/skills/req-change-workflow and .opencode/skills/req-change-workflow in your project.
What does Req Change Workflow need to run?
Going by SKILL.md and its folder, Req Change Workflow needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Req Change Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Req Change Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Req Change Workflow use?
Req Change Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Req Change Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Req Change Workflow?
Skills that share tags, products or a category with Req Change Workflow: Ad Review (CorridorTech/PoseCap, 224 stars), Req Change Workflow (aiskillstore/marketplace, 430 stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Knockoff Release Shipper (Shpigford/chops, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Req Change Workflow?
yunshu0909 (a GitHub user) maintains it in yunshu0909/yunshu_skillshub, which has 767 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 6, 2026.
Source: yunshu0909/yunshu_skillshub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.