@odysseus0

pull fetches origin/main and merges it into the current branch with structured conflict resolution guidance, preferring zdiff3 merge style for clarity and requiring explicit intent analysis before accepting either side.

commit produces git commits with conventional formatting, extracting intent from session history and validating staged changes against the commit message before finalizing.

push automates branch synchronization to origin, creates or updates pull requests, and enforces validation gates before shipping. handles non-fast-forward conflicts by delegating to pull skill and distinguishes sync problems from auth failures.

linear covers graphql operations against the linear api via a client tool, but lacks actionable procedures, trigger phrases, failure handling, and meaningful documentation beyond api mechanics.

Land a PR by monitoring conflicts, resolving them, waiting for checks, and

Investigate stuck runs and execution failures by tracing Symphony and Codex