args.io/bkdevs/args (link)

commit signals (85)

source signals (27)

• s2-sdk/CLAUDE.mdvia claude-code

  # CLAUDE.md — s2-sdk
  
  Rust SDK for [S2](https://s2.dev/), a durable streams platform. Provides async Rust bindings for managing basins, streams, and records.
  
  ## Module Overview
  
  | Module | Role |
  |--------|------|
  | `ops.rs` | Public API: `S2`, `S2Basin`, `S2Stream` |
  | `client.rs` | HTTP transport, connection pooling, auth |
  | `api.rs` | `AccountClient` / `BasinClient`; protobuf + S2S protocol |
  | `types.rs` | `S2Config`, `S2Error`, input/output DTOs |
  | `producer.rs` | High-level `Producer`: per-record

• s2-common/CLAUDE.mdvia claude-code

  # s2-common
  
  Shared library crate for S2 durable streams. Provides common types, serialization primitives, and utilities consumed by `s2-api`, `s2-sdk`, and `s2-server`.
  
  ## Module Overview
  
  | Module | Purpose |
  |--------|---------|
  | `record` | Core record types, binary encoding, batching |
  | `types` | Basin/stream naming, config, access control, pagination |
  | `maybe` | `Maybe<T>` — distinguishes "not provided" from explicit `None` (used for PATCH semantics) |
  | `read_extent` | `ReadLimit` and `ReadUnti

• args-server-common/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-server-common` houses Axum server utilities shared across the backend binary
  crates — `args-server`, `args-auth`, and `args-consumer`. It holds no
  business logic and no HTTP handlers; it is a library of reusable startup
  helpers, request extractors, middleware, and the config types they read.
  
  ## Structure
  
  - `bootstrap.rs` — process startup helpers: `load_env` (dotenvy),
    `i

• args-git-hooks/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-git-hooks` is the single native binary that implements args's server-side
  git hooks. It replaces the previous bash hook scripts (which lived in
  `args-core/hooks/` and were written into every repo's `hooks/` dir).
  
  It is deployed once at a fixed path (e.g. `/usr/local/bin/args-git-hooks`) and
  symlinked into a shared hooks directory that repos reach via `core.hooksPath`.
  The crate 

• args-core/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-core` contains all business logic, data access, and external client integrations. The backend server depends on this crate and calls its services.
  
  ## Structure
  
  ```
  src/
  ├── service/       Trait + Impl per domain (business logic)
  ├── repository/    Trait + Impl per domain (sqlx data access)
  ├── client/        Trait + Impl for external services (git2, git http-b

• args-metrics/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-metrics` is the standalone Axum HTTP server for product telemetry ingestion. Today it accepts batched web-vital events from the frontend and writes them to ClickHouse via `MetricsService` (defined in `args-core`). Like the other binary crates, it's a thin transport layer — no business logic lives here.
  
  ## Structure
  
  - `app.rs` — Router construction, middleware stack, `ArgsMe

• args-cli/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Architecture
  
  The binary is named `args`. Entry point: `src/bin/main.rs` → initializes rustls (`bootstrap::load_rustls()`) → parses CLI args → routes to the chosen command.
  
  ### Shipped commands
  
  The shipped commands, including the read-only current-branch `branch tail`
  workflow, are wired through `src/command.rs`.
  
  ### Command flow
  
  Each command follows: `load config → build client →

• args-slack-bot/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this directory.
  
  ## What this is
  
  A Slack bot for **args**, living as a Python/uv project inside the args monorepo (it is not a Cargo workspace member). Users invoke `/args <subcommand>` (`login`, `subscribe`, `unsubscribe`, `help`); the bot also exposes an HTTP webhook that args's main server calls back to finalize OAuth and post in-Slack notifications. Slack-Bolt runs in **HTTP mode** (not socket mode), wrap

• CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
  
  ## Project Overview
  
  Args is a GitHub alternative for open-source maintainers. It's a full-stack application with a Rust backend (Axum), TypeScript frontend (Next.js), and CLI tool.
  
  ## Workspace Structure
  
  Rust crates in the workspace:
  
  - **`args-api`** — Shared API resource types and endpoint request/response definitions.
  - **`args-api/derive`** (`args-api-derive`) — Proc macro crate pr

• s2-api/CLAUDE.mdvia claude-code

  # s2-api
  
  API types and protocol definitions for S2, a durable streams service. Acts as the shared contract layer between S2 clients and servers.
  
  ## Purpose
  
  - Define request/response types for basins (containers) and streams (append-only logs)
  - HTTP protocol extraction via Axum extractors (feature-gated)
  - Binary S2S streaming protocol with compression
  - Server-Sent Events (SSE) for resumable reads
  - Format negotiation: JSON, Protobuf, Base64
  
  ## Module Structure
  
  ```
  src/
    lib.rs              — expor

• args-consumer/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-consumer` is a long-running Kafka consumer that subscribes to `args.repo.pushed`, looks up the Slack webhooks subscribed to each repo's `Push` events, and notifies the args Slack bot server. Like the other binary crates, it's a thin shell — message handling logic lives in `WebhookService` (defined in `args-core`).
  
  ## Structure
  
  - `app.rs` — `ArgsConsumer` entrypoint: bootstr

• args-server/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-server` is the Axum HTTP server. It's a thin layer — handlers extract request params, call core services, and map responses. Business logic lives in `args-core`.
  
  ## Structure
  
  - `app.rs` — Router construction, middleware stack, `ArgsServer` entrypoint
  - `app/app_state.rs` — `AppState` with all service instances. Feature-gated fields for `main` vs `ci`.
  - Auth: handlers imp

• s2-server/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code when working with code in the `s2-server` crate.
  
  ## Overview
  
  `s2-server` is a lightweight HTTP server implementing the [S2](https://s2.dev) durable streams API, backed by object storage via SlateDB. It manages **basins** (logical containers) and **streams** (append-only logs), with pluggable storage backends (S3, GCP, local filesystem, or in-memory).
  
  Binary flags:
  ```
  --local-root DIR         Local filesystem backend root
  --port PORT              Li

• args-auth/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-auth` is the standalone Axum HTTP server for authentication flows: device-code login, GitHub OAuth, session refresh, email verification, and Slack account linking. It's a thin layer — handlers extract request params, call `AuthenticationService` (defined in `args-core`), and map responses. No business logic lives here.
  
  ## Structure
  
  - `app.rs` — Router construction, middlewa

• args-git-http-server/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-git-http-server` is the Axum HTTP shim for the git smart-HTTP protocol (clone, fetch, push).
  It is the "HTTP caller" in front of the gRPC [`args-git-server`](../args-git-server): it terminates
  HTTP, does **auth + authz + HTTP framing**, and delegates the raw git bytes to `args-git-server` over
  the `args-git-proto` gRPC schema. This mirrors GitLab's `workhorse` → `gitaly` split.

• args-internal-server/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-internal-server` is the Axum server for the **localhost-only receive-hook callback API** (the
  `/internal/*` routes). `args-git-server`'s `post-receive` / `proc-receive` hooks call back into it after a push to persist
  commits, reconcile bugs, create/update reviews, and publish the resulting Kafka events. It trusts its
  caller and is expected to run network-gated (localhost / privat

• args-api/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-api` defines the shared API contract — resource types (response shapes) and endpoint definitions (request/response pairs with HTTP metadata). Used by both the backend (to type handlers) and potentially clients.
  
  ## Structure
  
  - `resource/` — Data structs returned by the API. One file per domain: `auth`, `build`, `common`, `migration`, `organization`, `repository`, `review`, `

• args-web/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
  
  See the root `CLAUDE.md` for overall project context and backend architecture.
  
  **Environment:** Requires `.env.local` with `SUPABASE_URL`, `SUPABASE_PUBLISHABLE_KEY`, and optionally `ARGS_SERVER_URL` (defaults to `http://localhost:8080`).
  
  ## Route Structure
  
  App Router with route groups:
  
  - `(auth)/` — Public auth pages: login, signup, `/oauth/device` (CLI device flow), onboarding
  - `(blo

• args-git-router/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-git-router` is a gRPC front door for `args-git-server`. It speaks the same
  `args-git-proto` schema and, per call, peeks the method's declared **access mode**
  (the `access_mode` method option in `args_git.common.v1`) and reroutes the
  request to the matching upstream — read-only → replica, read-write → primary.
  
  Unlike `args-git-server`, this crate **depends on a database** (

• args-git-server/CLAUDE.mdvia claude-code

  # CLAUDE.md
  
  This file provides guidance to Claude Code (claude.ai/code) when working with code in this crate.
  
  ## Purpose
  
  `args-git-server` is a standalone gRPC server that owns git-on-disk operations — like GitLab's
  Gitaly. It is the single place other args services reach git through; consumers talk to it over the
  `args-git-proto` gRPC schema. It is deliberately **DB-free and does not depend on `args-core`** — the
  dependency direction is `consumers → args-git-proto (client) → args-git-server → 

• .claude-plugindirectoryvia claude-code
• args-plugins/claude/.claude-plugindirectoryvia claude-code
• args-plugins/claude/skills/revise/SKILL.mdvia unspecified

  ---
  name: revise
  description: Start tailing args comments on the current branch and respond to them live by making immediate code edits, absorbing and pushing after each change
  disable-model-invocation: true
  ---
  
  Start a persistent monitor that runs `args branch tail`, which lists any
  outstanding comments on the current branch and then follows new ones as they
  are posted. This command only tails comments — it does not push anything —
  so edits must be absorbed and pushed separately with `args absorb`.
  
  #

• args-plugins/codex/skills/revise/SKILL.mdvia unspecified

  ---
  name: revise
  description: Start tailing args comments on the current branch and respond to them live by making immediate code edits, absorbing and pushing after each change
  ---
  
  Run `args branch tail` as a long-lived shell process. It lists any outstanding
  comments on the current branch and then follows new ones as they are posted.
  This command only tails comments — it does not push anything — so edits must
  be absorbed and pushed separately with `args absorb`.
  
  ## Steps
  
  1. Start `args branch tail` 

• args-plugins/claude/skills/commit/SKILL.mdvia unspecified

  ---
  name: commit
  description: Stage the changes made in this session, commit with a written message, and push to the current remote branch
  disable-model-invocation: true
  ---
  
  Stage the changes made during this conversation, commit them, and push the
  result to the remote tracking branch for whatever branch is currently checked
  out.
  
  ## Steps
  
  1. **Review what's changing.** Run `git status` and `git diff` to see staged
     and unstaged changes before touching anything. If anything looks like it
     might contai

• args-plugins/codex/skills/commit/SKILL.mdvia unspecified

  ---
  name: commit
  description: Stage the changes made in this session, commit with a written message, and push to the current remote branch
  ---
  
  Stage the changes made during this conversation, commit them, and push the
  result to the remote tracking branch for whatever branch is currently checked
  out.
  
  ## Steps
  
  1. **Review what's changing.** Run `git status` and `git diff` to see staged
     and unstaged changes before touching anything. If anything looks like it
     might contain secrets, flag it to the user 

• .agentsdirectoryvia unspecified

ignorefile signals (4)