[blooop]

Summary by Sourcery

Update the project template to improve tooling, cloud IDE support, and dependency versions.

New Features:

• Add built-in configuration and documentation for using the project with the Claude Code online environment, including activation and session start hooks.

Enhancements:

• Document ruff as both formatter and linter and clarify rocker-based VS Code container configuration in the README.
• Switch pixi configuration to workspace mode and add shellcheck as a dependency.
• Bump versions of test and tooling dependencies in pyproject.toml.
• Update CI and devcontainer tooling versions, including actions/checkout, setup-pixi, and pixi itself.
• Refresh rocker container base image and arguments configuration.
• Update the recorded project version in the changelog to 0.2.0.

CI:

• Update GitHub Actions workflows to use newer actions/checkout and setup-pixi versions and clean up dependabot configuration patterns.

Documentation:

• Add dedicated documentation for Claude Code integration under .claude/README.md and extend the main README with Claude Code usage instructions.

[sourcery-ai]

Reviewer's Guide

Updates the Python project template from the latest upstream, adding Claude Code online environment support, modernizing tooling and CI versions, and refreshing development/dependency configuration.

Flow diagram for Claude Code SessionStart hook behavior

flowchart TD
  Start[Start_Claude_Code_session] --> Hook[Run_.claude/hooks/SessionStart]

  Hook --> CheckPixi{Is_pixi_installed?}
  CheckPixi -->|No| InstallPixi[Install_pixi_binary]
  CheckPixi -->|Yes| SkipInstallPixi[Skip_pixi_install]

  InstallPixi --> InstallDeps
  SkipInstallPixi --> InstallDeps[Install_project_dependencies_with_pixi]

  InstallDeps --> SetupPreCommit[Set_up_pre_commit_hooks]
  SetupPreCommit --> ConfigureGit[Configure_git_merge_drivers_for_lockfiles]

  ConfigureGit --> Done[Environment_ready_for_pixi_commands]

  Done --> UseCommands[User_runs_pixi_run_test_lint_format_ci]

Loading

File-Level Changes

Change	Details	Files
Document and wire up Claude Code online environment support for this template.	Extend README to describe Claude Code integration, automatic environment setup, and manual activation instructions. Add .claude/README.md describing SessionStart hook behavior, available pixi tasks, troubleshooting, and customization options. Introduce .claude/activate.sh helper script for activating the pixi environment from an interactive shell. Add .claude/hooks/SessionStart hook script (implementation not shown in diff) that runs on Claude Code session start to bootstrap the environment.	README.md .claude/README.md .claude/activate.sh .claude/hooks/SessionStart
Refresh development tooling versions, dependencies, and CI configuration.	Switch pixi configuration from a project to a workspace table and add shellcheck as a managed dependency. Relax and bump upper bounds for core test/dev Python packages (pylint, pytest, pytest-cov, hypothesis, ruff, coverage, pre-commit). Update GitHub Actions to newer versions of actions/checkout and prefix-dev/setup-pixi. Update devcontainer Dockerfile to install a newer pixi release. Adjust Dependabot configuration dev-dependencies group to drop black from the grouped patterns and normalize whitespace. Update CHANGELOG version from 0.0.0 to 0.2.0. Regenerate or update pixi.lock, devcontainer, VS Code, and docs intro files to align with the new template (content not shown in diff).	pyproject.toml .github/workflows/ci.yml .github/workflows/pre-commit.yaml .devcontainer/Dockerfile .github/dependabot.yml CHANGELOG.md pixi.lock .devcontainer/devcontainer.json .vscode/tasks.json docs/intro.rst
Tweak environment and container setup defaults for docker/rocker workflows.	Update rocker configuration to use Ubuntu 24.04 base image and adjust rocker args from nvidia to jquery while keeping other flags. Clarify README legacy section to reference rockerc.yaml instead of deps_rocker/dbw.deps.yaml for container configuration.	rockerc.yaml README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 2 issues, and left some high level feedback:

• The .github/workflows/ci.yml and .github/workflows/pre-commit.yaml workflows reference actions/checkout@v6, but the latest published major version is v4, so these should be pinned to a valid existing tag to avoid workflow failures.
• The new .claude/hooks/SessionStart file appears to be empty while .claude/README.md describes fairly extensive setup behavior; consider either implementing the described logic in this hook or scaling back the README description to match what actually runs.
• In rockerc.yaml the args entry was changed from nvidia to jquery, which looks like a likely typo or misconfiguration for rocker features and may cause container builds to fail or omit GPU support if that was intended.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `.github/workflows/ci.yml` and `.github/workflows/pre-commit.yaml` workflows reference `actions/checkout@v6`, but the latest published major version is `v4`, so these should be pinned to a valid existing tag to avoid workflow failures.
- The new `.claude/hooks/SessionStart` file appears to be empty while `.claude/README.md` describes fairly extensive setup behavior; consider either implementing the described logic in this hook or scaling back the README description to match what actually runs.
- In `rockerc.yaml` the `args` entry was changed from `nvidia` to `jquery`, which looks like a likely typo or misconfiguration for rocker features and may cause container builds to fail or omit GPU support if that was intended.

## Individual Comments

### Comment 1
<location> `rockerc.yaml:10` </location>
<code_context>
+image: ubuntu:24.04
 args:
-  - nvidia
+  - jquery
   - x11 
   - user 
</code_context>

<issue_to_address>
**issue (bug_risk):** Double-check the `jquery` rocker arg, it looks unrelated to typical rocker feature flags like `nvidia`.

This entry used to be `nvidia`, which is the standard rocker feature for GPU-enabled images. `jquery` is not a known rocker feature and will likely be ignored or confuse future maintainers. If this change wasn’t intentional, please revert to `nvidia` or another valid feature flag.
</issue_to_address>

### Comment 2
<location> `.claude/activate.sh:5-8` </location>
<code_context>
+# Usage: source .claude/activate.sh
+
+# Add pixi to PATH
+export PATH="$HOME/.pixi/bin:$PATH"
+
+# Optional: Activate pixi shell if available
</code_context>

<issue_to_address>
**suggestion:** Avoid repeatedly prepending `$HOME/.pixi/bin` to PATH when the script is sourced multiple times.

Because this script is intended to be sourced, it may be run multiple times in the same shell, causing `$HOME/.pixi/bin` to be prepended repeatedly. Consider guarding it with a check such as:

```sh
case :$PATH: in
  *:$HOME/.pixi/bin:*) ;;
  *) export PATH="$HOME/.pixi/bin:$PATH" ;;
esac
```

or an equivalent approach so the entry is only added once.

```suggestion
# Add pixi to PATH (only once)
case ":$PATH:" in
    *:"$HOME/.pixi/bin":*)
        # Already present, do nothing
        ;;
    *)
        export PATH="$HOME/.pixi/bin:$PATH"
        ;;
esac

# Optional: Activate pixi shell if available
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

suggestion: Avoid repeatedly prepending $HOME/.pixi/bin to PATH when the script is sourced multiple times.

Because this script is intended to be sourced, it may be run multiple times in the same shell, causing $HOME/.pixi/bin to be prepended repeatedly. Consider guarding it with a check such as:

case :$PATH: in
  *:$HOME/.pixi/bin:*) ;;
  *) export PATH="$HOME/.pixi/bin:$PATH" ;;
esac

or an equivalent approach so the entry is only added once.

Suggested change

	# Add pixi to PATH
	export PATH="$HOME/.pixi/bin:$PATH"
	# Optional: Activate pixi shell if available
	# Add pixi to PATH (only once)
	case ":$PATH:" in
	*:"$HOME/.pixi/bin":*)
	# Already present, do nothing
	;;
	*)
	export PATH="$HOME/.pixi/bin:$PATH"
	;;
	esac
	# Optional: Activate pixi shell if available