typemux-cc AGENTS.md

Agent Instructions

Landing the Plane (Session Completion)

When ending a work session, complete the steps below.

WORKFLOW:

1. Run quality gates (if code changed) - make all
2. Report remaining work - Describe follow-up work without creating issues unless the user explicitly authorizes issue creation
3. Report the working tree - Summarize changed files and verification results
4. Hand off - Provide context for the next session

Creating issues, committing, pushing, and opening pull requests are separate external mutations. Perform each one only when the user explicitly authorizes that action. An instruction to commit does not authorize a push or pull request, and an instruction to push does not authorize opening a pull request.

---

typemux-cc - Python Type-Checker LSP Multiplexer for Claude Code

See README.md for project overview. See docs/ARCHITECTURE.md for architecture details.

Build & Quality

# REQUIRED: Run before completing any work
make all          # format + lint + test

# Individual commands
make fmt          # cargo fmt
make lint         # cargo clippy -- -D warnings
make test         # cargo test

Git Workflow (MUST FOLLOW)

⚠️ NEVER commit directly to main. Always use feature branches.

1. BEFORE any code changes: Create a feature branch

   git checkout -b feat/your-feature-name
   

2. After changes: Run quality checks

   make all  # format + lint + test
   

3. Update documentation: If user-facing behavior changes, update README.md
4. Commit, when explicitly authorized: Use conventional commits (feat:, fix:, docs:, etc.)
5. Push, when explicitly authorized: Never merge directly to main

   git push -u origin <branch-name>
   

6. Create a pull request, when explicitly authorized

   gh pr create
   

Pre-Commit Checklist

Before committing, verify:

• On a feature branch (not main)?
• make all passes?
• README.md updated if needed?
• The user explicitly authorized the commit?