{ }
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.
Designed for
Small engineering teams that want autonomous repo help but still want humans owning scope, review, and merge decisions
Operating goal
Turn routine maintenance issues into clean pull requests with tests, logs, and a clear human review boundary.
4 steps from trigger to verified handoff, with success and failure paths.
1 MCP layer and 4 connected tools with explicit auth and risk levels.
3 guardrails, 3 evals, and 1 harnesses before production use.
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.
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, refine it with the agent chat, then generate the architecture or product board from the same workflow spec.
Open in Agent WorkflowA Slack-native engineering agent that receives operational requests, gathers context from tickets and repos, routes work to specialist agents, and drafts auditable responses before anything risky happens.
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.
A code review workflow that watches pull requests, assigns specialist reviewers, checks implementation risk, and posts concise review notes with links to evidence.