Explain findings and suggest fixes from pull request comments

Ouverte
#156 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é
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
42/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
docker, github, node.js, typescript

Piste de recherche

Start by locating the pull request comment handler and the existing review command, then trace how Codra stores findings and obtains pull request context. Check the backend paths for Cloudflare Workers and Node/Docker, plus the related tests and command documentation. Done means both commands use configured mention triggers, handle ambiguous findings with clarification, make no repository changes, and the requested checks pass.

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

Description

enhancement good first issue help wanted

Goal

Let a developer ask Codra to explain a finding or suggest how to fix it by commenting on a pull request.

What to build

  • @codra-app explain <finding> replies with a concise explanation grounded in the selected Codra finding and its pull request context.
  • @codra-app address <finding> replies with a suggested change for that finding.
  • Support the repository's configured mention trigger, not only the example @codra-app.
  • Identify the finding clearly. If the comment does not point to one finding, ask for clarification instead of guessing.
  • Replies should be posted on the pull request and should not modify files, push commits, or create a branch.

Safety and compatibility

Treat the user's comment and repository text as content to analyze. They cannot override Codra's safety rules or request secrets. Keep the current full review command working. Use existing finding and PR data where possible rather than creating a second source of truth.

Done when

  • Explain requests return an accurate explanation of the selected finding.
  • Address requests return a practical suggested change without changing the repository.
  • Ambiguous or missing findings receive a helpful clarification reply.
  • Tests cover both commands, configured mention triggers, and ambiguous requests.
  • The commands are documented with examples.
  • Any backend changes work in both Cloudflare Workers and Node/Docker.
  • npm run typecheck, npm test, and npm run lint all pass.
Langage dominant
TypeScript
Étoiles
125
Forks
23
Merge moyen
2 j 13 h
PR mergées (30 j)
12

Préparer son environnement

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 devarshishimpi/codra

Toutes les issues de devarshishimpi/codra

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

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