PR Description

A clear description for every pull request. Comment @cloudaeye /describe, and CloudAEye writes the title, description, change summary, and considerations from the code changes and commit history.

Book a demo All use cases

From commits to a clear description.

Comment @cloudaeye /describe on a pull request. CloudAEye reads its code changes and commit history and writes a structured description, ready for you to review and edit.

GitHubpayments-api #318

Pull request #318

Update retry4 commits

No description provided.

  • add RETRY_CAP
  • fix loop
  • validation
  • readme

You@cloudaeye /describe

Generated description

Make the payment retry cap configurablePR title

Description

Lets operators set how many times a failed payment is retried, instead of a fixed three attempts.

Change summary

  • payments/config.ts reads and validates the new RETRY_CAP setting.
  • payments/retry.ts stops after RETRY_CAP attempts.
  • README.md documents the setting.

Implementation details

RETRY_CAP is read once at startup and falls back to 3 when it is not set.

Additional considerations

Values below 1 are rejected at startup. Existing deployments keep three attempts until the setting is changed.

A draft to review and edit before you rely on it.

Reviewers start
with the why.

A good description tells reviewers what changed, why, and where to look closely. CloudAEye writes it from the code, so no pull request opens empty.

Never open an empty PR.

Generate a description from the code changes and commit history, so reviewers have context from the first look.

  • Empty descriptionWritten from the code
  • Brief noteExpanded with detail
  • ResultA draft you edit
See an example

Many commits, one story.

Commits that build one feature are summarized as one coherent change, not a list of messages to piece together.

  • ReadsCode changes and commits
  • ExplainsPurpose and scope
  • ListsKey changes and files
Read the docs

Cross-file changes, explained.

Changes that span files and components get a structured summary of what changed in each file, so reviewers can find their way through the diff.

  • OverviewPurpose and scope
  • Per fileWhat changed
  • ReviewersKnow where to look
See it on a real PR

Consistent PRs across teams.

Every pull request gets the same structure. Developers refine it to their team's conventions instead of writing from scratch.

  • PR titleA concise summary
  • Change summaryKey modifications
  • ConsiderationsTesting, docs, compatibility
Explore PR Walkthrough

Commands

Claude Code
/cloudaeye:describe
Codex
$cloudaeye:describe
GitHub · Bitbucket · GitLab
@cloudaeye /describe

In Claude Code or Codex, it describes the change on your machine, ready to paste into the pull request.