Agent Persona Exploration - 2026-11-10

Ouverte Adaptée aux débutants
  • Quelque chose ne va pas ?
#76,552 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
69/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github-actions, go
Domaine
ai-infra-agents, documentation

Piste de recherche

Commencez par lire les trois guides indiqués : .github/aw/safe-outputs-content.md, .github/aw/create-agentic-workflow-trigger-details.md et .github/aw/create-agentic-workflow.md. Vérifiez le comportement documenté par GitHub de l’événement milestoned avant de modifier les indications sur le trigger. Le travail est terminé lorsque les guides traitent des numéros de cible explicites, de la réserve et de la protection concernant le milestone, ainsi que de la proposition de valeurs par défaut pour les termes non définis, étiquetées comme valeurs par défaut.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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 · ◷

Langage dominant
Go
Étoiles
5.6k
Forks
615
Merge moyen
5 h 21 min
PR mergées (30 j)
792

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de github/gh-aw

Toutes les issues de github/gh-aw

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.