Add a dossier skill that turns failed runs into readable files

Fermée
  • Quelque chose ne va pas ?
#25 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

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

Une pull request liée a déjà été fusionnée.

  • #42 par @gregogun — fusionnée

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
57/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
markdown, node.js, playwright, typescript
Domaine
developer-experience, testing

Piste de recherche

Start with the existing doctor script and its node --test regression tests, then inspect the skill authoring validation, build, and current Claude Code hook docs. Add the dossier script, skill, optional hook, go-help row, README entry, and fixture tests described in the acceptance criteria. Done means hostile titles produce a correctly quoted reproduce command, both error shapes show their messages, and the validation and build pass.

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

Description

ready-for-agent

Parent

#15

What to build

An agent with a red test run gets a short markdown dossier for each failure instead of a wall of runner output. A new dossier skill ships a script that reads Playwright's JSON report and writes one file per failure. Each file holds the error, the location, the screenshot, the trace path, and a command that reproduces the failure. The skill tells the agent to read the trace before changing code, starting from the action that took far longer than the others. The skill also offers an optional hook that runs the script when a test command fails.

The reproduce command runs exactly the failing test, even when the test title contains $, backticks, or quotes. Each failure shows its message whether the report puts it in error or in errors.

Acceptance criteria

  • The course's script, run as written, shows each bug: a hostile title breaks the reproduce command, and a failure stored in errors has an empty message. The PR description records both runs. A bug that does not reproduce is dropped, and the PR gives the command that disproved it.
  • After the fix, the same inputs produce a correct reproduce command and a message for every failure. The reproduce command uses POSIX single-quote escaping.
  • A node --test regression test runs the script on a fixture report with hostile titles and both error shapes, as the doctor tests do for their script.
  • The optional hook runs the script after a failed test command, and its payload shape matches current Claude Code hook docs.
  • The skill has a go-help row and a README line, and passes the authoring-a-skill validation and the build.

Which Playwright version the fixture report comes from, and whether the script supports a second runner now, are left to the build.

Langage dominant
JavaScript
Étoiles
0
Forks
0
Merge moyen
1 j 3 h
PR mergées (30 j)
37

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

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 gregogun/gstack

Toutes les issues de gregogun/gstack

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

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