Agent Persona Exploration - 2026-11-12

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

从 issue 中的三条建议开始：.github/aw/network.md，以及 .github/aw/create-agentic-workflow.md 第 103 行和第 255 行附近的指导。阅读这些部分并与上面的发现进行比较；当文档涵盖 registry 查询示例、用于结构检查的确定性预处理，以及在 prompt 摘要中放置默认值时，即告完成。

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

描述

agent-research cookie
Persona Overview
  • Agent: agentic-workflows
  • Personas This Run: Frontend Developer, DevOps Engineer, QA Tester
  • Rotation: all 9 personas are now covered, so the rotation resets next run
  • Scenarios Tested: 4 of 6 generated (FE-5, DO-5, DO-6, QA-5); FE-6 and QA-6 were not tested
  • Invocation: one persona-evaluator run; all 4 scenarios returned recommendations
  • Average Quality Score: 4.5/5.0
  • Run: §43248107250
Key Findings
  • Triggers were correct in all four recommendations: pull_request with path filters for PR reviews, and schedule plus workflow_dispatch for the scheduled check. Trigger appropriateness averaged 5.0.
  • All four used read-only permissions, no edit tool, pull_request rather than pull_request_target, and COMMENT-level reviews that do not block PRs.
  • The weakest dimensions were completeness (4.0) and prompt clarity (4.25). Defaults the agent chose (exemption matching, the 48-hour cron rule, Go subtest rules) were written in the notes but often missing from the prompt summary.
  • DO-6 was the only over-broad network suggestion. It hardcoded four registries, although the containers ecosystem already covers GHCR and Docker Hub.
  • No scenario averaged below 4.4.
Top Patterns
  1. Triggers: pull_request with paths: filters (3 of 4); schedule plus workflow_dispatch (1 of 4).
  2. Tools: github gh-proxy and bash in all four. Shell commands handled file listing, test scanning, and CLI lookups.
  3. Safe outputs: review comments (FE-5, QA-5), a rolling add-comment with hide-older-comments (DO-6), and create-issue with close-older-issues (DO-5). noop appeared in all four.
View Scenario Scores
Scenario Task Trigger Tools Security Prompt Completeness Avg
FE-5 Storybook story gap on component PRs 5 5 5 4 4 4.6
DO-5 Scheduled workflows silent for 48h 5 5 5 4 4 4.6
DO-6 Unpinned Dockerfile base images 5 4 4 5 4 4.4
QA-5 Test functions with no assertions 5 4 5 4 4 4.4
View High Quality Responses
  • FE-5 (4.6): Inline COMMENT-level review per component missing a story, honors the exemption list, caps at max: 25, and calls noop when nothing is missing. Read-only, no network.
  • DO-5 (4.6): Treats disabled workflow states as out of scope and marks crons longer than 48 hours as not evaluated rather than stale. close-older-issues with a key dedupes the tracking issue.
View Areas for Improvement
  • DO-6: Hardcodes quay.io, gcr.io, mcr.microsoft.com, and public.ecr.aws. The same response says to limit hosts to registries the repo names. It also assumes crane or docker buildx is available without checking, and does not say whether to pin the index digest or a per-platform digest.
  • QA-5: Detects test functions with grep/awk, which is brittle for Go and TypeScript. The Go subtest and t.Skip-only rules appear only in the notes.
  • FE-5, DO-5, QA-5: Exemption matching, the story file pattern, and the 48-hour cron rule are labelled defaults in the notes but missing from the prompt summaries.
Recommendations
  1. .github/aw/network.md: Add a worked example for registry-backed lookups. Prefer ecosystem identifiers such as containers, and add FQDNs only for registries that the repository files actually name.
  2. .github/aw/create-agentic-workflow.md: For structural checks (test-function detection, digest resolution), recommend deterministic steps: that write to /tmp/gh-aw/ so the agent only formats results. The guidance at line 255 covers this only for large-data preprocessing.
  3. .github/aw/create-agentic-workflow.md: Line 103 already asks for labelled Default: values. Require that they also appear in the prompt summary, not only in the notes.

References:

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

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

环境准备

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