build: mention @claude in github to get work done

[lklimek]

Installs Claude Code so that we can mention @claude during code review and give it some tasks.

Uses my (@lklimek) personal Claude subscription for now. Can be replaced with Claude API key in the future.

This pull request introduces automation and environment setup improvements for Claude Code integration, ensuring consistency between local development and CI environments. It adds a session start hook to install required dependencies and pre-download proto sources, configures Claude Code hooks, and introduces a GitHub Actions workflow for Claude Code. Additionally, it updates development guidelines to enforce conventional commit naming.

Claude Code integration and automation:

• Added .github/workflows/claude.yml to run Claude Code workflows in response to comments or PR reviews mentioning @claude, ensuring Claude Code automation is triggered appropriately.
• Added .claude/settings.json to configure a session start hook for Claude Code environments, running the new setup script on startup.

Development environment setup:

• Introduced .claude/hooks/session-start.sh script to automate installation of required system packages, Rust components, protoc, and to pre-download Tenderdash proto sources, ensuring local environments match CI and builds do not fail due to missing dependencies or network issues.

Development process guidelines:

• Updated CLAUDE.md to require PRs and commits to follow conventional commit naming rules, promoting consistency in commit history.

Installs protoc v25.2, clippy, rustfmt, and system dependencies
(clang, cmake, libsqlite3-dev, libzmq3-dev) to match CI workflows.
Only runs in Claude Code remote environments.

https://claude.ai/code/session_01SdEvmPYuJkJoAVJejB8Tz9

Summary by CodeRabbit

• Chores

  • Automated development environment setup for remote coding sessions to streamline prerequisite installation and configuration.
  • Added CI/CD workflow integration for automated code review processes.

• Documentation

  • Updated development guidelines for commit naming conventions and code formatting standards.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Adds Claude Code integration infrastructure including a session-start Bash script for remote environment setup (protoc, Rust, system packages, pre-downloaded dependencies), configuration file defining hooks, and GitHub Actions workflow enabling Claude Code execution on repository interactions.

Changes

Cohort / File(s)	Summary
Claude Code Setup .claude/hooks/session-start.sh, .claude/settings.json	Session-start script initializes remote environment with idempotent installation of build dependencies (protoc v25.2, Rust components, system packages), pre-downloads Tenderdash proto sources to optimize builds, and configures Cargo environment variables. Settings file defines SessionStart hook configuration with 120-second timeout.
GitHub Integration .github/workflows/claude.yml	Workflow triggers Claude Code Action on issue comments, PR review comments, issue opens/assigns, and PR review submissions when @claude token is present, with appropriate permissions for repository access.
Documentation CLAUDE.md	Adds guidelines for conventional commit naming and reminders to run clippy and nightly formatting before finalizing work.

Sequence Diagram

sequenceDiagram
    actor Developer
    participant GitHub as GitHub
    participant Workflow as GitHub Actions
    participant ClaudeAction as Claude Code Action
    participant Remote as Remote Environment
    participant Script as session-start.sh

    Developer->>GitHub: Comment with `@claude`
    GitHub->>Workflow: Trigger workflow
    Workflow->>ClaudeAction: Execute Claude Code Action
    ClaudeAction->>Remote: Connect to remote environment
    Remote->>Script: Execute session-start.sh
    Script->>Script: Install protoc (if needed)
    Script->>Script: Install Rust components
    Script->>Script: Install system packages
    Script->>Script: Pre-download Tenderdash sources
    Script->>Script: Configure Cargo environment
    Script->>Remote: Return ready environment
    Remote->>ClaudeAction: Environment initialized
    ClaudeAction->>Developer: Ready for code operations

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

🐰 A rabbit hops through CI/CD streams,
With hooks and scripts fulfilling dreams,
Protoc installed, Tenderdash cached below,
Claude's remote garden ready to grow! 🌱

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title mentions @claude and GitHub but is vague about the actual changes; it doesn't clearly convey that this integrates Claude Code automation, adds build environment setup, or configures a session-start hook.	Consider a more specific title that describes the primary change, such as: 'build: integrate Claude Code automation and environment setup' or 'ci: add Claude Code workflow and session initialization'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch claude/setup-github-actions-9t98i

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[lklimek]

@claude check if this PR builds

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.claude/hooks/session-start.sh:
- Around line 103-111: The script appends a second [env] table which produces
invalid TOML if CARGO_CONFIG_FILE already contains an [env] section; update
session-start.sh to detect whether an [env] table exists (searching for a line
matching "^\[env\]") and if present, ensure TENDERDASH_DIR and CARGO_TARGET_DIR
keys are added/updated beneath that existing [env] block (instead of appending a
new [env] header); if no [env] exists, create the [env] block as currently done.
Use CARGO_CONFIG_FILE, TENDERDASH_DIR and TENDERDASH_CACHE_DIR as the target
symbols to find and insert/update the key=value lines atomically (or employ a
TOML-aware tool) so the file remains valid TOML.

🧹 Nitpick comments (1)

.claude/hooks/session-start.sh (1)

60-60: Hardcoded Tenderdash version requires manual sync with build.rs.

The comment on Line 59 notes this must match DEFAULT_VERSION in rs-tenderdash-abci/proto/build.rs. If that version is bumped without updating this script, the pre-download becomes useless and builds will attempt (and potentially fail) network fetches again. Consider extracting this to a shared constant or adding a CI check that validates the versions match.

[lklimek]

Hardcoded Tenderdash version requires manual sync with build.rs.

The comment on Line 59 notes this must match DEFAULT_VERSION in rs-tenderdash-abci/proto/build.rs. If that version is bumped without updating this script, the pre-download becomes useless and builds will attempt (and potentially fail) network fetches again.

@claude Implement a solution that will detect required version of tenderdash automatically.

[lklimek]

@claude check if you can build this project

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/clippy.yml:
- Around line 56-60: The "Install Rust toolchain" step currently uses
dtolnay/rust-toolchain@master with toolchain: "1.92", which diverges from
tests.yml's dtolnay/rust-toolchain@stable; update the clippy workflow to match
the tests workflow strategy by either switching the "uses" to
dtolnay/rust-toolchain@stable (and remove the explicit "toolchain" pin) or pin
both workflows to the same explicit toolchain string (e.g., change toolchain in
clippy.yml and tests.yml so both use "1.92"), editing the Install Rust toolchain
step (uses and/or toolchain fields) so both workflows run the identical Rust
version.

🧹 Nitpick comments (4)

.github/workflows/clippy.yml (1)

67-74: PROTOC env var is step-scoped — won't be visible during build

The env: PROTOC on lines 73–74 is scoped to the "Install protoc" step only. If any build.rs (e.g., protobuf code generation) checks the PROTOC environment variable rather than searching PATH, it won't find it during the clippy or fmt steps. Since protoc is installed to /usr/local/bin (which is on PATH), this likely works in practice, but it would be cleaner to either move the PROTOC env to the job level or remove it entirely.

Suggested fix: promote to job-level env

 env:
   CARGO_TERM_COLOR: always
+  PROTOC: /usr/local/bin/protoc

and remove the step-level env block on lines 73–74.

.github/workflows/tests.yml (1)

56-57: Consider pinning the Rust toolchain version to match clippy.yml

Using @stable without a version pin means the tests workflow will automatically pick up new stable releases. While this catches forward-compatibility issues early, it also means CI can break unpredictably on a new Rust release day. The clippy workflow pins "1.92" — aligning both would give more deterministic builds.

Suggested change

      - name: Install Rust toolchain
-        uses: dtolnay/rust-toolchain@stable
+        uses: dtolnay/rust-toolchain@master
+        with:
+          toolchain: "1.92"

.github/workflows/claude.yml (2)

21-26: Broad write permissions — ensure this is intentional.

contents: write grants Claude the ability to push commits directly. Combined with pull-requests: write and issues: write, this gives the action significant repository access. This is expected for the Claude Code action workflow, but worth confirming the team is comfortable with this scope — especially since any GitHub user who can comment @claude on a public issue/PR could trigger it.

Consider whether restricting triggers to specific users/teams (e.g., via an additional if check on github.actor) would be appropriate for your threat model.

---

37-37: User-specific secret creates a bus-factor risk.

CLAUDE_CODE_OAUTH_TOKEN_LKLIMEK is tied to a single developer. If that person leaves or their token is rotated, this workflow silently breaks. Consider using a team/org-level secret (e.g., CLAUDE_CODE_OAUTH_TOKEN) or a machine account token instead.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/claude.yml:
- Around line 21-26: Remove the unnecessary id-token: write permission from the
workflow permissions block (the id-token key) since this job uses direct
Anthropic API authentication via anthropic_api_key rather than cloud provider
authentication; update the permissions list to omit id-token while leaving other
permissions (contents, pull-requests, issues, actions) unchanged to reduce the
workflow's security surface.

[lklimek]

@claude in session-start.sh, update protoc to the most recent version

[lklimek]

@claude in session-start.sh, update protoc to the most recent version

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

CLAUDE.md (1)

17-17: ⚠️ Potential issue | 🟡 Minor

Remove nightly requirement from formatting instructions.

Lines 17 and 36 document conflicting formatting commands: line 17 specifies cargo fmt --all, while line 36 specifies cargo +nightly fmt. Since rust-toolchain.toml pins the project to stable Rust 1.92 and no nightly-specific rustfmt configuration exists, the +nightly requirement should be removed.

Change line 36 from cargo +nightly fmt to cargo fmt --all to match line 17.

🧹 Nitpick comments (1)

CLAUDE.md (1)

9-9: Clarify which conventional commit standard to follow.

The guideline mentions "conventional commit naming rules" but doesn't specify which standard. Consider referencing the Conventional Commits specification (e.g., feat:, fix:, docs:, chore:, etc.) or provide examples to make this more actionable for contributors.

📝 Suggested clarification

-- PR and commits should follow conventional commit naming rules.
+- PR and commit messages should follow the [Conventional Commits](https://www.conventionalcommits.org/) specification (e.g., `feat:`, `fix:`, `docs:`, `chore:`).