Bitbucket pull request review brief
Read-only review brief for one Bitbucket Cloud pull request. It reads repository metadata, pull request details, comments, commits, commit statuses, and recent pipelines through recued-core.bitbucket, then asks the AI summarizer for scope, discussion state, CI state, risks, and next actions. It never posts comments, approves, requests changes, declines, merges, edits pull requests, runs pipelines, changes branches, or calls arbitrary Bitbucket APIs.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (22 steps)
workspace
trim
Trim whitespace from setting workspace
repo_slug
trim
Trim whitespace from setting repo slug
repository
?
pull_request
?
comments_raw
?
commits_raw
?
statuses_raw
?
pipelines_raw
?
comments
default
Apply default
commits
default
Apply default
statuses
default
Apply default
pipelines
default
Apply default
comment_rows
slice
Take a subset of
commit_rows
slice
Take a subset of
comment_count
count
Count items in comments
commit_count
count
Count items in commits
status_count
count
Count items in statuses
pipeline_count
count
Count items in pipelines
summarize
?
comment_table
to_table
Format results as a data table
commit_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
focus
setting
=
Summarize pull request scope, author and reviewer state, comment themes, commit activity, commit status and pipeline health, merge risks, and concrete next actions. Do not invent facts outside the Bitbucket records.
bitbucket
setting
=
repo slug
setting
=
row limit
setting
=
25
workspace
setting
=
max length
setting
=
900
pull request id
setting
=
0
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.