Normalize what exists.
Read the minimum provider metadata needed to describe repositories, pull requests, environments, deployments, and preview branches.
Product
From pull request to preview resource—and back again.
LintCycle builds a read-only lifecycle map across GitHub, Railway, and Supabase, then turns gaps in that map into explainable findings.
The lifecycle model
Inventory first. Correlate second. Recommend last.
The order matters. A single old timestamp is not enough evidence to call infrastructure stale.
Connect resources to work.
Match provider resources with their originating repository and pull request using deterministic identifiers and lifecycle signals.
Name the broken loop.
Classify stale, orphaned, missing, or unhealthy resources only when the available evidence clears the rule threshold.
Keep the action human.
Acknowledge, snooze, ignore, or resolve the finding. Complete any provider change manually in the provider itself.
Evidence before confidence
Every finding shows its working.
The resource, linked work, rule, evidence, confidence, and recommended manual action stay together.
Finding / Railway environmentHigh confidence
preview/pr-284 is still active.
The linked pull request was merged 12 days ago. Three independent signals agree on the correlation.
- GitHub
- PR #284 · merged
- Railway
- Environment · active
- Rule
- Merged PR + retained preview
- Recommendation
- Review the environment manually
Conservative by default
Unclear correlation is not a finding.
Infrastructure naming is messy. When signals conflict or the originating work cannot be identified with enough confidence, LintCycle withholds the recommendation instead of dressing ambiguity up as certainty.
What the queue supports
Review state without changing provider state.
Acknowledge
Record that someone has reviewed the finding and understands the resource state.
Snooze or ignore
Quiet a known exception while keeping the reason attached to the organization-scoped record.
Resolve
Close the finding after the team verifies the lifecycle, without giving LintCycle destructive provider capability.
Close the loop
Bring the whole preview lifecycle into view.
Start with one workspace, ten repositories, and the complete read-only product.