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

[Safe Outputs Conformance] MCE-001: add_comment tool description lacks explicit CONSTRAINTS/IMPORTANT disclosure wording

已关闭 适合新手
#71,061 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions, go
领域
devtools

调研方向

阅读 pkg/workflow/js/safe_outputs_tools.json 中 add_comment 工具的说明,以及 scripts/check-safe-outputs-conformance.sh 中的 MCE-001 检查。添加必需的 CONSTRAINTS 或 IMPORTANT 说明,同时保留现有的限制措辞和 WRITE-ONCE 指引。运行 bash scripts/check-safe-outputs-conformance.sh;完成意味着 MCE-001 通过,且现有限制检查保持不变。

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

描述

automated conformance safe-outputs
Conformance Check Failure

Check ID: MCE-001
Severity: MEDIUM
Category: Specification (Section 8.3 MCE2)

Problem Description

Per spec Section 8.3 MCE2, the add_comment MCP tool description MUST surface its enforcement constraints, including an explicit CONSTRAINTS/IMPORTANT-style disclosure. The current description in pkg/workflow/js/safe_outputs_tools.json (around line 531) already documents the numeric limits (524288 char input limit, 10 mentions, configured max-links, 65536-char published comment limit) but opens with WRITE-ONCE: do NOT probe this tool... rather than a CONSTRAINTS: or IMPORTANT labeled block, so the keyword check fails even though the limits themselves are present.

Affected Components
  • Files: pkg/workflow/js/safe_outputs_tools.json (add_comment tool description, line ~531)
  • Check: scripts/check-safe-outputs-conformance.sh function check_mce_constraint_disclosure (MCE-001)
<b>Current vs Expected Behavior</b>
Current Behavior

Description text: WRITE-ONCE: do NOT probe this tool with empty or placeholder arguments. If not ready to post a real comment, call noop. ... Input is limited to 524288 characters, 10 mentions, and configured max-links URL occurrences (default: 50). Oversized agent content is automatically replaced by notices to fit the complete 65536-character published comment. ...

Expected Behavior

The description should include a clearly labeled constraints block (containing the literal word CONSTRAINTS or phrasing like IMPORTANT constraint) so agents and tooling can reliably locate the enforcement limits, per Requirement MCE2.

Remediation Steps
  1. Edit the add_comment entry in pkg/workflow/js/safe_outputs_tools.json (line ~531) to add an explicit CONSTRAINTS: prefix (or IMPORTANT constraint: phrasing) ahead of the existing limit disclosures, e.g. prepend CONSTRAINTS: input limited to 524288 characters, 10 mentions, and configured max-links URL occurrences (default: 50); ... while keeping the existing WRITE-ONCE guidance intact.
  2. Keep all currently-passing sub-checks intact (65536 char limit, 10 mention limit, max-links default 50 phrasing) when rewording.
  3. Regenerate/recompile any workflows that embed this tool definition if required by make recompile.
Verification

After remediation, verify the fix by running:

bash scripts/check-safe-outputs-conformance.sh

MCE-001 should pass without errors.

References
  • Safe Outputs Specification: docs/src/content/docs/specs/safe-outputs-specification.md
  • Conformance Checker: scripts/check-safe-outputs-conformance.sh
  • Run: §39729823556
  • Date: 2026-10-22

Generated by ✅ Daily Safe Outputs Conformance Checker · claude · agent · 132.9 AIC · ⌖ 0.552 AIC · ⊞ 5.4K · ◷

  • expires on Oct 22, 2026, 9:54 PM UTC-08:00
主要语言
Go
星标
5.4k
派生
596
平均合并
3 小时 51 分钟
30 天内合并 PR
831

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

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

从这里开始

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

github/gh-aw 的其他 Issue

查看 github/gh-aw 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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