connectrpc-axum

Run the complete test suite for connectrpc-axum. Use when the user asks to run tests, verify changes, or check if the code works.

Reference for project architecture. Use when you need to understand the codebase structure, module organization, request/response flow, or key types.

Compare a GitHub repository with connectrpc-axum. This skill should be used when the user provides a GitHub repository URL and wants to compare it with the current project. Analyzes user features, technical implementation, architecture patterns, code quality, tests, and documentation. Outputs comparison to docs/guide/compare/ directory.

Reference the LOCAL connect-go/ directory for ConnectRPC protocol. NEVER use WebFetch/WebSearch for github.com/connectrpc/connect-go - always read local files.

Create integration tests for connectrpc-axum. Use when the user wants to add a new Rust client test or Rust server test for the integration test suite.

Investigate and resolve GitHub issues for connectrpc-axum. Requires a GitHub issue link or number. Analyzes the issue, references architecture docs and connect-go implementation, creates integration tests if needed, then posts a resolution plan or answer.

Handle user questions, feature requests, and bug reports for connectrpc-axum. This skill should be used when users ask questions about the library, request new features, or report bugs. It first attempts to answer using project documentation, verifies bugs with integration tests, and submits GitHub issues when needed.

Sync documentation with main branch changes. This skill should be used when the user wants to update VitePress documentation to reflect changes made on the main branch. It compares origin/docs against local main, analyzes new commits, and updates relevant documentation files in parallel.

Reference the LOCAL tonic/ directory for gRPC client implementation patterns. NEVER use WebFetch/WebSearch for github.com/hyperium/tonic - always read local files.