Recued
Menu
← Back to recipes

Neon branch readiness brief

by recued-core v1 10 views

Use “Neon branch readiness brief” in Recued. It provides a read-only Neon branch readiness brief for one project branch.

How it works 21 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (21 steps)
normalized_project_id trim
Trim whitespace from setting project id
normalized_branch_id trim
Trim whitespace from setting branch id
project ?
branch ?
endpoints_raw ?
databases_raw ?
roles_raw ?
operations_raw ?
defaults defaults
Apply defaults
endpoint_count count
Count items in endpoints
database_count count
Count items in databases
role_count count
Count items in roles
operation_count count
Count items in operations
summarize ?
endpoint_rows slice
Take a subset of
database_rows slice
Take a subset of
operation_rows slice
Take a subset of
endpoint_table to_table
Format results as a data table
database_table to_table
Format results as a data table
operation_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

neon setting =
focus setting = Summarize this Neon branch's current state, compute endpoint health, databases, roles, recent operations, readiness risks, and concrete next steps. Do not invent facts outside the Neon data.
branch id setting =
row limit setting = 20
max length setting = 900
project id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Read your Neon connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

neon neonpostgresdatabasebranchescomputeoperationsai-summarypack:neon

Details

21 steps 6 configurable settings recipe_id: branch-readiness-brief-neon