Agent Persona Exploration - 2026-11-10

未关闭 适合新手
  • 哪里不对？
#76,552 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
69/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions, go
领域
ai-infra-agents, documentation

调研方向

首先阅读指定的三份指南：.github/aw/safe-outputs-content.md、.github/aw/create-agentic-workflow-trigger-details.md 和 .github/aw/create-agentic-workflow.md。编辑 trigger 指南前，先检查 GitHub 文档中关于 milestoned 事件行为的说明。完成条件是这些指南涵盖明确的目标编号、milestone 的注意事项和保护措施，以及为未定义术语提出默认值并标注为默认值。

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

描述

agent-research cookie
Persona Overview
  • Agent: agentic-workflows
  • Personas This Run: Program Manager, Designer, Legal / Compliance
  • Scenarios Tested: 3 of 6 generated (PGM-4, DSG-4, LEG-6)
  • Average Quality Score: 4.3/5.0 (3 of 3 invocations succeeded)
Key Findings
  • All three invocations succeeded. Each returned one recommendation covering trigger, tools, permissions, network access, and safe outputs.
  • Every recommendation used deny-by-default network (allowed: []), read-only contents, no edit tool, and allowlisted labels or reviewers.
  • Prompt clarity was the lowest dimension (4.0). Ambiguous terms (freeze-date format, what counts as uncertain, tracker location) were left as open questions rather than given defaults.
  • PGM-4 scored lowest (4.0). The agent itself flagged target: "*" as too broad.
  • The average is slightly below the last two runs (4.6 and 4.4). Three scenarios are too few to call that a trend.
Top Patterns
  1. Triggers: pull_request with paths: filters for file-scoped checks (DSG-4, LEG-6); issues: milestoned for event-driven milestone checks (PGM-4), matching the decision table in .github/aw/create-agentic-workflow-trigger-details.md.
  2. Tools: the default github toolset plus default bash for static checks. No edit or playwright in any recommendation.
  3. Security: network: allowed: [] in all three, allowlisted add-labels and reviewer teams, and explicit noop branches.
View Scores by Scenario
Scenario Trigger Tools Security Prompt Completeness Average
PGM-4 (Program Manager, issue) 4 4 4 4 4 4.0
DSG-4 (Designer, PR) 5 4 4 4 5 4.4
LEG-6 (Legal / Compliance, PR) 4 5 5 4 4 4.4
View High Quality Responses (Top 2-3)
  • DSG-4 (4.4): Path-filtered pull_request trigger. Explicit allowed values (currentColor, none, inherit, url(#...)) and a defined path for files that cannot be checked (invalid XML, external references, size limit). Says clearly that the checks are structural and do not judge contrast or title quality.
  • LEG-6 (4.4): Routes uncertain cases to a legal reviewer and a label instead of deciding them. Minimal permissions and no network. The per-image table is easy to act on.
View Areas for Improvement (Top 2-3)
  • PGM-4 target: "*": lets the agent comment on any issue. Restricting targets to the triggering issue and the tracker by number would fix it. Its own caveat says the same.
  • PGM-4 milestone read via gh api inside the agent: in this environment gh is not authenticated for reads, so the pattern may fail if copied. The .github/aw/ docs place gh api calls in deterministic steps (for example workflow-patterns.md). The milestone read could move to a pre-agent step. Not verified against the runtime.
  • DSG-4 SVG checks as ad hoc Python: a deterministic pre-agent step, as run 42644982485 recommended for FE-3, would make results reproducible and limit the agent to reading output.
  • Undefined terms: the agent deferred definitions (freeze-date format and timezone, what counts as uncertain) to the user. A proposed default, marked as a default, would be more actionable.
Recommendations
  1. In .github/aw/safe-outputs-content.md, advise against target: "*" when a workflow acts on the triggering item plus one named tracker. List explicit numbers instead.
  2. In .github/aw/create-agentic-workflow-trigger-details.md, add a caveat to the milestone trigger row. The evaluator says milestoned may not fire for issues created directly into a milestone. Check the GitHub docs for the event behaviour before documenting it, then recommend a guard.
  3. In .github/aw/create-agentic-workflow.md, require ad hoc evaluations to propose a default for undefined terms and label it as a default, instead of listing them only as open questions.

References: §42844667323, §42644982485, §42494947077

Generated by 🎭 Agent Persona Explorer · claude · routed: haiku55 xhigh · ~8 AIC · ⌖ ~2 AIC · ⊞ 7.6K · ◷

主要语言
Go
星标
5.6k
派生
615
平均合并
5 小时 21 分钟
30 天内合并 PR
792

环境准备

在 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 摘要。