Skip to content

feat: Add agentready assessment workflow#5989

Closed
ntkathole wants to merge 2 commits intofeast-dev:masterfrom
ntkathole:agentready-assessment
Closed

feat: Add agentready assessment workflow#5989
ntkathole wants to merge 2 commits intofeast-dev:masterfrom
ntkathole:agentready-assessment

Conversation

@ntkathole
Copy link
Member

@ntkathole ntkathole commented Feb 19, 2026

What this PR does / why we need it:

Add a GitHub Actions workflow that runs AgentReady assessments on pull
requests, pushes to main/master, and manual dispatch. Posts the assessment report as a PR comment when triggered by a
pull request.


Open with Devin

@ntkathole ntkathole self-assigned this Feb 19, 2026
devin-ai-integration[bot]

This comment was marked as resolved.

@ntkathole ntkathole force-pushed the agentready-assessment branch from 1a6a8ad to 915bc23 Compare February 19, 2026 12:59
devin-ai-integration[bot]

This comment was marked as resolved.

@ntkathole ntkathole force-pushed the agentready-assessment branch from 915bc23 to a23da73 Compare February 19, 2026 13:02
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
devin-ai-integration[bot]

This comment was marked as resolved.

devin-ai-integration[bot]

This comment was marked as resolved.

Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
@ntkathole ntkathole force-pushed the agentready-assessment branch from c151d14 to 49bfe0e Compare February 19, 2026 13:22
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 new potential issue.

View 6 additional findings in Devin Review.

Open in Devin Review

Comment on lines +73 to +78
await github.rest.issues.createComment({
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
body: report
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 PR comment spam: createComment creates a new comment on every push instead of updating existing one

The workflow triggers on pull_request with types [opened, synchronize, reopened], meaning it runs on every push to the PR branch. The "Comment on PR" step uses github.rest.issues.createComment() which creates a new comment each time, rather than finding and updating an existing AgentReady comment.

Impact and suggested approach

For an active PR with many pushes, this will flood the PR with duplicate AgentReady assessment comments — one per push. This makes the PR conversation noisy and hard to follow.

The standard pattern for bot comments in GitHub Actions is to:

  1. Search for an existing comment with a known marker (e.g., <!-- agentready-assessment -->)
  2. If found, update it with github.rest.issues.updateComment()
  3. If not found, create a new one with github.rest.issues.createComment()

This is the approach used by most CI bots (coverage reporters, size checkers, etc.) to keep PR conversations clean.

Prompt for agents
In .github/workflows/agentready-assessment.yml, lines 51-78, modify the "Comment on PR" step's script to find and update an existing comment instead of always creating a new one. The approach:

1. Add a marker string like `<!-- agentready-assessment -->` to the comment body.
2. Before creating a comment, list existing comments on the PR using `github.rest.issues.listComments()` and search for one containing the marker.
3. If found, use `github.rest.issues.updateComment({ comment_id: existingComment.id, ... })` to update it.
4. If not found, use `github.rest.issues.createComment()` to create a new one.

Example pattern:

const marker = '<!-- agentready-assessment -->';
const body = marker + '\n' + report;
const { data: comments } = await github.rest.issues.listComments({
  issue_number: context.issue.number,
  owner: context.repo.owner,
  repo: context.repo.repo,
});
const existing = comments.find(c => c.body && c.body.includes(marker));
if (existing) {
  await github.rest.issues.updateComment({
    comment_id: existing.id,
    owner: context.repo.owner,
    repo: context.repo.repo,
    body: body,
  });
} else {
  await github.rest.issues.createComment({
    issue_number: context.issue.number,
    owner: context.repo.owner,
    repo: context.repo.repo,
    body: body,
  });
}
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@ntkathole ntkathole marked this pull request as draft February 19, 2026 13:31
@ntkathole ntkathole closed this Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants