Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

fix(app-control): make /app-control:drive keep the control-skill floors' caller duties

未关闭 适合新手
#9,667 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
85/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
markdown, shell
领域
cli, documentation

调研方向

阅读 plugins/app-control/reference/control-skill.md 中的 Safety floors 部分,了解调用方的三项职责。编辑 plugins/app-control/skills/drive/SKILL.md,写明每个账户一次登录的规则、exit-4 被阻止的规则,以及何时传入 --attended 和 --yes。当 drive 的 SKILL.md 包含这三点时即完成。

由索引模型根据 Issue 内容生成。

描述

needs-human priority: medium status: ready work-class: scoped

Problem

The control-skill contract (plugins/app-control/reference/control-skill.md, "Safety floors", added in #9628) gives the caller that runs a feature's ## Drive steps three duties the stateless driver CLI cannot carry:

  • call cli/ sign-in <account> at most once per account per run, and stop the run on a failed attempt;
  • read exit 4 as refused by a floor and record the step blocked, never retry it;
  • pass --attended only when a person is present, and --yes for a granted production write only after the person said yes in this session.

/app-control:map keeps these during its own proof (plugins/app-control/skills/map/reference/prove.md). /app-control:drive runs those same steps on every plain run, and plugins/app-control/skills/drive/SKILL.md names none of them: it cites the contract only as "the shape a control skill follows". Found in the ready-flip code review of #9628.

Fix

Add the three caller duties to drive's SKILL.md (or a pointer to the contract's Safety floors section that drive reads before running Drive steps), keeping attended use as guidance, not enforcement (owner decision on #9581).

Done when

  • drive's SKILL.md states the one-sign-in-per-account rule, the exit-4 blocked rule, and when it passes --attended and --yes.
主要语言
Shell
星标
22
派生
2
平均合并
3 小时 15 分钟
30 天内合并 PR
949

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

melodic-software/claude-code-plugins 的其他 Issue

查看 melodic-software/claude-code-plugins 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。