tadado-release skillA
tadado-release is agent-read markdown (skill) from hananxr/tadado: Tadado2 的**发布流程**（项目级，只在本仓库用）：验收 → 打包 → 提交 → 推送 → 打 tag / 发 Release → 同步 skill 到本机。触发词：发布、发版、打包、重打包、提交、推送、上线、release、打 tag、 传安装包、同步 skill。在 Tadado 仓库里提到「提交 / 推送 / 打包 / 发布」时用本 skill —— 它规定每一步的顺序与**安全约束**（尤其是「谁有权推送」）。.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Tadado2 发布流程 本 skill 服务的是**这个仓库**：把「代码改完了」变成「用户手上有一个新安装包，仓库也同步了」。 > ⚠️ 动手前先读两份东西：仓库根的 **`CLAUDE.md`**（项目约定与命令）与 **`TODO.md` 末尾两条** > （最近这轮做了什么、有没有留下没做完的事）。它们比本文件更贴近当下。 ## 一次发布 = 五步 | # | 做什么 | 能不能跳 | |:--:|---|---| | 1 | **验收**：`npm run e2e` | 动过 `desktop/` 或 `resources/skill/**` 就不能跳 | | 2 | **打包**：`npm run tauri build` + 便携 zip + 迁移 skill 的 zip | 同上；没动代码可以跳 | | 3 | **提交**：`git add` + **一次** commit | 不能（有改动就得提交） | | 4 | **推送**：`git push`、tag、`gh release create` | **用户明确说推才推** ← 见铁律 | | 5 | **同步 skill**：仓库 → 本机 `.claude/skills/` | 动过 `resources/skill/` 就不能跳 | ## 铁律（这一节比后面所有步骤都重要） - **推送是用户的动作，不是你的。** `git push`、`gh release create` 必须在用户**明确要求**后才做。 用户只说「提交」时，做到 commit 为止，然后把该敲的推送命令**原样打给他**，不要自己补上。 - **绝不 force push** —— `--force`、`--force-with-lease` 都不行，`main` 上尤其不行。 （`main` 在 GitHub 上**已经开了分支保护**：`Block force pushes` + `Restrict deletions`， enforcement = Active。真去 force push 会被远端拒掉 —— 但**别把它当挡箭牌**，本地这一层也要守住； 也**不要**为了绕开它去点 `Allow force pushes`。） - **绝不 `--no-verify`**。hook 拦下来就去看为什么，不要绕过。 - **绝不改 `git config`**（用户名、邮箱、remote 一个都不动）。 - **`--amend` 只在用户明确要求时用**；用之前先 `git log -1 --format='%an %ae'` 确认那条提交是自己的。 …
Read the whole file at its exact version.
How to install
mdr add hananxr/tadado/tadado-release@git:20260921.6ccf14amdr add hananxr/tadado/tadado-release@sha256:3265be08a41fe9c5Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_tf476b5a5xsxwor2)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.6ccf14a latest | 2026-09-21 | 6ccf14a | 16,319 B | A | view · diff |
| git:20260921.859ce05 | 2026-09-21 | 859ce05 | 15,817 B | A | view · diff |
| git:20260921.965db2d | 2026-09-21 | 965db2d | 15,518 B | A | view · diff |
| git:20260921.1d42756 | 2026-09-21 | 1d42756 | 14,530 B | A | view · diff |
| git:20260921.b064504 | 2026-09-21 | b064504 | 11,713 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16319 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hananxr/tadado · 23 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tf476b5a5xsxwor2 GET https://markdownregistry.com/api/v1/resolve?ref=hananxr/tadado/tadado-release GET https://markdownregistry.com/api/v1/blob/3265be08a41fe9c5da0828646191a73500d67524ffd111a17512d074b68f425d
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.