Nodeflow release prep

Use for app release preparation, store readiness, signing, screenshots, privacy/compliance, build checks, or release checklists.From its SKILL.md

Install

npx -y skills add CAI5946/NodeFlow --skill nodeflow-release-prep

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

4.2 KB, as published. Nobody here has run it

Reply in Chinese.
Treat release work as high-risk.
Check before changing.
Do not generate legal claims, privacy statements, pricing, or store promises without user-provided facts.
Do not expose or commit secrets, signing keys, API keys, or keystore files.
Confirm before changing version, signing config, store text, or release assets.
For Flutter projects, run Flutter commands in the app directory when needed.
When reporting a release-blocking issue, include a reproduction flow when it can be reproduced by command, build step, store-console step, or device operation.
After approved release changes, verification must include concrete manual steps; for app releases, include real-device smoke-test steps.

When waiting for confirmation, treat 1 as confirmation to continue with the current pending step.
When asking the user to choose from numbered options, treat 1 as selecting option 1 instead.

If the user only invokes this skill, provide an empty template.
If the user invokes this skill with an initial idea, conservatively prefill only fields clearly supported by the user's text.
Leave uncertain fields empty. Do not write 待补充.
Do not infer version numbers, legal/compliance content, signing configuration, platform, pricing, or release assets.
Ask the user to confirm or complete the template before entering Phase 1.

If details are missing, provide this template and ask the user to confirm or complete it:

请按下面模板补充发布信息：

1. 发布目标：
2. 平台：
3. 应用名称：
4. 当前版本：
5. 发布类型：
6. 已准备材料：
7. 需要 Agent 做什么：
8. 不允许改动：
9. 验收标准：

Read relevant docs/configs only as needed. Output:

## 问题 / 目标理解

## 修改必要性

## 最佳方案

## 需要修改的文件

## 不会改动的内容

## 风险与影响

## 验证方式

等待你确认后再执行。

Do not modify files in this phase.

Only edit or run build steps after explicit approval.

Possible checks:

Privacy policy, user agreement, foreground service declaration if applicable.
App icon, feature graphic, screenshots, store title, short description, full description.
Version name/code.
Signing config and .gitignore protection.
Debug flags, hardcoded secrets, logging level.
Crash/analytics readiness if used.
Flutter build, such as flutter build appbundle.
Closed testing checklist.

After execution, output:

## 执行内容

## 修改文件

## 构建 / 检查结果

## 实机测试步骤

## 仍缺失内容

## 上架前人工确认

## 最终结论

Stop and ask before continuing if:

A secret, keystore, or signing config may be exposed.
Store/legal content lacks factual input.
Build requires credentials not available locally.
Release commands fail and the next step could change signing, versioning, or store state.