Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Agent Persona Exploration - 2026-10-18

オープン 初心者向け
  • 何か問題がありますか？
#69,944 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
70/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, markdown
領域
documentation

調査の方向性

.github/aw/create-agentic-workflow.md にある定期ダイジェストの推奨事項と既存のパターンに関するガイダンスを読みます。schedule、create-issue、close-older-issues、およびエンティティと時間枠でスコープを限定した重複排除キーを含む、名前付きパターンを追加します。ガイドにこの再利用可能なパターンが記載されれば完了です。issue には実行すべきテストが指定されていません。

索引モデルが issue の本文から書いたものです。

説明

agent-research
Persona Overview
  • Agent: agentic-workflows custom agent (via persona-evaluator sub-agent)
  • Personas This Run: Product Manager, Program Manager, QA Tester
  • Scenarios Tested: 4 of 6 generated (PM2-3, PRG-3, QA-3, QA-4)
  • Average Quality Score: 4.85/5.0
Key Findings
  • All 4 scenarios received strong, production-ready recommendations (no score below 4 on any dimension).
  • The agent consistently defaults to least-privilege read-only permissions and empty network.allowed: [] even when not explicitly asked.
  • For "visibility over time" asks (milestone risk, test-health trend), it correctly reframes them as scheduled digests rather than forcing an event trigger.
  • It proactively designs dedup keys (close-older-issues + per-entity title prefixes) to prevent duplicate tracking issues across runs.
  • It independently flagged a cross-scenario collision risk (two scheduled report workflows using the same create-issue/close-older-issues pattern) and specified distinct dedup keys to avoid interference.
Top Patterns
  1. Triggers: pull_request (scoped to specific types, same-repo only) for inline review tasks; schedule + workflow_dispatch for periodic digests; workflow_run with a precise if: gate (run_attempt > 1) for rerun-based detection.
  2. Tools: github MCP in gh-proxy mode with the minimal toolset needed (actions: read only when reading CI artifacts/logs); cache-memory: true for cross-run trend baselines.
  3. Security practices: read-only permissions scoped per-field (contents, issues, pull-requests, actions), no network access granted for analysis-only tasks, explicit noop conditions defined for every scenario.
View High Quality Responses (Top 3)
  • PM2-3 (Product Manager, PR automation): Resolves the roadmap issue via closing keywords, diffs PR scope against the issue's acceptance-criteria checklist, and posts a single rolling comment (hide-older-comments: true) instead of spamming the thread on every push.
  • QA-3 (QA Tester, issue automation): Uses workflow_run gated on run_attempt > 1 as a precise, low-noise trigger for flaky-test detection, and dedups tracking issues by test name (not commit) so recurring flakiness consolidates into one issue.
  • QA-4 (QA Tester, scheduled): Uses cache-memory to persist the prior week's baseline for trend comparison, and correctly distinguishes "no data" (report with a note) from "noop" (zero qualifying runs) — avoiding an over-eager noop that would hide a real reporting gap.
View Areas for Improvement (Top 2)
  • No weak responses were observed this run, so there is less adversarial signal than usual — all 4 scenarios tested were already well-aligned with authoring guidance, which may indicate the subset chosen (PR/schedule/workflow_run triggers) is already a "solved" pattern space for the agent. Future runs should include an issue-triggered or on-demand scenario to probe less-tested trigger types.
  • The recurring "scheduled digest + create-issue + close-older-issues" pattern appeared independently in both PRG-3 and QA-4; while the agent self-corrected with distinct dedup keys, this pattern recurring unprompted across unrelated scenarios suggests it's worth codifying explicitly rather than relying on the agent to re-derive it each time.
Recommendations
  1. Add the "recurring digest" pattern (schedule + create-issue with close-older-issues: true and a dedup key scoped to <entity>:<time-window>) as a named, citable pattern in .github/aw/create-agentic-workflow.md, since it now appears independently across multiple unrelated personas/scenarios.
  2. Document the workflow_run + if: run_attempt > 1 gating technique for rerun/flakiness-detection workflows in .github/aw/github-agentic-workflows.md, as a reusable low-noise trigger condition.
  3. Next run, deliberately select at least one issues-event or workflow_dispatch-only scenario per persona to diversify trigger coverage beyond the PR/schedule/workflow_run space this run concentrated on.

Generated by 🎭 Agent Persona Explorer · claude · agent · 111.1 AIC · ⌖ 0.742 AIC · ⊞ 6.7K · ◷

主要言語
Go
スター
5.4k
フォーク
584
平均マージ
3時間 16分
マージ済み PR（30日）
829

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

github/gh-aw のほかの issue

github/gh-aw の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。