Agent Team template
A Claude Code-style workflow for scoped engineering maintenance: it reads issues, loads repo context, plans a narrow patch, runs checks, and opens a reviewable PR with evidence instead of pretending the merge is done.
One-message setup · 4 specialists · Instant sample
Designed for
Small engineering teams that want autonomous repo help but still want humans owning scope, review, and merge decisions
Outcome
Turn routine maintenance issues into clean pull requests with tests, logs, and a clear human review boundary.
Say what should be true when the work is done.
Codelit runs one labeled Sample with no account, model, or external App calls.
Review the evidence, then reuse the same brief with your data when it is useful.
Decides whether the task is narrow enough for autonomous work.
Claude code-capable reasoning model
Finds the minimum code and docs needed for the patch.
Long-context code model
Applies the smallest viable change on a branch.
Claude Code or Claude Agent SDK route
Runs checks and turns failures into evidence or limited fix attempts.
Code reasoning model
Loads the workflow goal, allowed actions, escalation policy, and output contract before the agent plans work.
A workflow skill that captures the operating contract, tool boundaries, and escalation rules for Claude Code: Repo Maintenance Agent.
Centralizes high-risk action checks for writes, secrets, customer data, billing, deploys, and public communications.
Exposes task resources, prompt templates, connector tools, and audit records behind a permission-aware boundary.
tools · resources · prompts
Classify task risk, ownership, and likely files.
Read instructions, code, tests, and ownership notes.
Create a branch and make the scoped change.
Run checks, summarize logs, and open a draft PR.
Open it in Codelit and describe the result. Codelit handles common setup while Flow stays available for direct editing and Activity keeps the proof.
Try agentTurns one scoped release request into a reviewed branch artifact, preview deployment, browser-verified result, pull request, production promotion, and Slack proof using the accounts the team already owns.
Correlates Sentry, Datadog, PagerDuty, and deployment evidence, proposes one bounded mitigation, pauses on the exact actions, and leaves status proof for responders.
A Devin-style engineering workflow that turns a scoped ticket into a branch, implementation plan, code changes, test run, and pull request draft with review evidence.