القائمة
Load ArcBlock company context (products, technical architecture, strategy) on demand. Use `/arcblock-context` to see available topics, or `/arcblock-context <topic>` to load specific context.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Process one GitHub issue end-to-end — read the issue + referenced repo docs/code + existing comments, verify against the landed implementation/intent, and post evidence-backed findings as a comment on the issue. Covers doc-review, doc-audit, system-audit, research, and idea issue types. Use when handling a single issue (issue-sweep calls this per issue).
Sweep open GitHub issues for unprocessed human input and act on each via the issue-review skill — delete-PRs for human-approved deprecated docs, doc-update PRs for approved drifted docs, fix-PRs for approved bugs, analysis+TDD-plan comments for feature/design requests (then implement after confirmation), close issues whose PR merged, comment-only on conditional/security/needs-decision ones. The actionable signal may be a comment OR the issue body. With --autofix-green, also auto-fixes "green" issues that have no human reply yet (unambiguous + verifiable-here + low-risk + non-security) — reproduce→fix→test→PR, never auto-merge. Run manually (/agentloop:issue-sweep) or on a schedule. Designed for a doc-audit + spin-off + feature workflow.
One-command setup/update of an agentloop FLEET on a teammate's machine or cloud — asks a few defaulted questions, then generates/reconciles the two config files (deployment.json + repos.json) and installs the schedule. LOCAL = a crontab marker-block wiring fleet/driver.ts (one row per skill; the driver fans out to every covered repo). CLOUD = one claude routine per (repo×skill) via RemoteTrigger, batch-created from the same catalog. Idempotent — re-run to upgrade. This is the SCHEDULING side that `bootstrap` (repo adoption) deliberately leaves out. Interactive — never runs unattended.
Independent clean-context review of ONE open GitHub pull request — read PR diff + linked issue + verify every claim against live code/tests + run the verification gate (pre-merge) and diagnose its root-cause + detect conflicts with sibling PRs, then emit an evidence-backed merge-readiness verdict (MERGE / COMMENT / SUPERSEDE / BLOCK / CLOSE). Runs verification every time (read-only safe); --post writes one verdict comment. Never auto-merges (that gated step belongs to pr-sweep). Use /agentloop:pr-review <pr#> for a single PR; pr-sweep batches this engine across all open PRs.
Batch-review every open GitHub PR and drive it to a terminal state autonomously — fan out a clean-context pr-review per PR (verify claims against live code, run the verification gate), cluster PRs by shared issue + shared files, DEDUP-CLOSE same-issue duplicates (keep the best one, comment + close the twin), and GATED auto-merge every verified non-breaking PR (docs/tests/fixes AND features) while escalating only security / breaking changes / architecture-direction decisions to a human. Designed to run on a schedule on an independent machine so PRs get reviewed + merged without a human in the loop. Run /agentloop:pr-sweep (review+comment+dedup-close only), /agentloop:pr-sweep --merge (also auto-merge gated PRs), or /agentloop:pr-sweep --dry-run (report only).
Iterative clean-context review of a design/plan document or issue — spawn independent-perspective reviewers each round, score, and synthesize findings without carrying prior-round bias. Use to review an implementation plan, architecture doc, or design proposal before building.
| name | arcblock-context |
| description | Load ArcBlock company context (products, technical architecture, strategy) on demand. Use `/arcblock-context` to see available topics, or `/arcblock-context <topic>` to load specific context. |
ArcBlock 公司知识库快速访问入口。
/arcblock-context # 显示可用主题列表
/arcblock-context <topic> # 加载特定主题
/arcblock-context all # 加载全部概览
检查用户是否提供了参数：
输出以下列表：
## ArcBlock 公司知识库
### 产品 (Products)
- `arcsphere` - AI-native 浏览器与 Shell
- `agent-fleet` - AI-native Blocklet 运行时
- `blocklet-server` - 部署平台
- `blocklet-developer` - 开发者心智模型
- `did-wallet` - 多链多资产身份钱包
- `docsmith` - AI-native 文档工具
- `paymentkit` - 抽象支付层
- `promotion-kits` - 增长驱动营销工具集
- `did-spaces` - 去中心化个人数据空间
- `did-connect` - 应用-钱包交互协议
- `did-names` - DID 原生域名系统
- `aigne` - AI 原生软件工程框架
- `aigne-hub` - LLM 后端统一管理服务
- `aistro` - AI 占星应用
- `discuss-kit` - 综合内容可组合 Blocklet
- `live-document` - AI Vibe Coding 时代的新出版形态
### 技术 (Technical)
- `afs` - Agentic File System
- `aine` - AI Native Engineering
- `did-capability` - 身份与能力
- `blocklet` - Blocklet/Chamber/Scaffold
- `abt-staking` - Staking for X 通用框架
- `nft-vc` - NFT 作为 Digital Twin
- `credittoken` - USD 计费合规设计
- `chain` - 链架构
### 战略 (Strategy)
- `strategy` - 公司战略方向
### 快捷方式
- `products` - 加载产品概览
- `technical` - 加载技术概览
- `all` - 加载全部概览
用法: `/arcblock-context <topic>`
示例: `/arcblock-context afs` 或 `/arcblock-context arcsphere`
根据参数加载对应文件：
| 参数 | 加载文件 |
|---|---|
| Products | |
arcsphere | products/arcsphere.md |
agent-fleet | products/agent-fleet.md |
blocklet-server | products/blocklet-server.md |
blocklet-developer | products/blocklet-developer.md |
did-wallet | products/did-wallet.md |
docsmith | products/docsmith.md |
paymentkit | products/paymentkit.md |
promotion-kits | products/promotion-kits.md |
did-spaces | products/did-spaces.md |
did-connect | products/did-connect.md |
did-names | products/did-names.md |
aigne | products/aigne.md |
aigne-hub | products/aigne-hub.md |
aistro | products/aistro.md |
discuss-kit | products/discuss-kit.md |
live-document | products/live-document.md |
| Technical | |
afs | technical/afs.md |
aine | technical/aine.md |
did-capability | technical/did-capability.md |
blocklet | technical/blocklet.md |
abt-staking | technical/abt-staking.md |
nft-vc | technical/nft-vc-design.md |
credittoken | technical/credittoken-design.md |
chain | technical/chain-architecture.md |
| Strategy | |
strategy | strategy/README.md |
| 快捷方式 | |
products | products/README.md |
technical | technical/README.md |
all | products/README.md + technical/README.md + strategy/README.md |
读取文件后，输出：
✓ 已加载: <文件名>
<文件中的高密度摘要或核心内容>
---
提示: 你现在可以询问关于 <主题> 的任何问题。
加载文件时按以下优先级查找：
./.claude/arcblock-context/{path}~/.claude/arcblock-context/{path}{path}User: /arcblock-context
Claude: [显示完整主题列表]
User: /arcblock-context arcsphere
Claude: ✓ 已加载: products/arcsphere.md
[输出 ArcSphere 摘要]
User: /arcblock-context technical
Claude: ✓ 已加载: technical/README.md
[输出技术架构概览]
User: /arcblock-context afs aine
Claude: ✓ 已加载: technical/afs.md, technical/aine.md
[输出两个主题的摘要]
加载上下文后，记住 ArcBlock 的核心原则：