mainline-org
Official@mainline-org
Mainline governs coding-agent behavior in Git repositories via intents, autonomy limits, stop lines, and commit/push/PR/merge boundary controls.
Agent Skills by mainline-org
Showing 1 vetted skills indexed across 1 GitHub repositories.
Frequently Asked Questions About mainline-org
FAQPage SchemaWhat tasks can I control using mainline-org's Mainline skill?▼
Mainline lets you define intents, autonomy limits, and stop lines for coding agents in Git repos. It governs committing, pushing, opening PRs, PR descriptions, and merge/release/deploy boundaries, including auto-submit, auto-commit, and auto-seal behavior through hooks, proposals, gaps, and conflict handling.
Who should use the Mainline skill?▼
Engineers running coding agents inside Git repositories who need enforceable boundaries on agent actions. It suits teams that want inspect_or_stop checkpoints, current-instruction overrides, and controlled commit/seal handoffs rather than unrestricted agent commits, pushes, or PR creation.
How does Mainline enforce boundaries during a coding session?▼
Mainline uses configured hooks such as before_commit, proposed_intent, and opened_pr to intercept agent actions. When an action exceeds the allowed_boundary or hits a stop line, the agent must inspect_or_stop, escalating to proposals or flagging gaps and conflicts instead of proceeding.
What prerequisites are needed to use Mainline?▼
You need a Git repository where a coding agent operates and where Mainline is set up or being adopted. The skill applies when configuring agent_authority, max_autonomy, intents, and boundary rules for commit, push, PR review, merge, release, and deploy stages.