agent-readiness-report: scan_build_env.sh misses lowercase `justfile` and `just` build commands

Open Beginner friendly
#955 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@austinchennn is already working on this.

Since Nov 19, 2026.

  • #966 by @austinchennn — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bash
Domain
tooling

Research direction

Start with plugins/onboarding/skills/agent-readiness-report/scripts/scan_build_env.sh, especially the file checks around lines 21 and 31 and the build command grep around line 23. Read the scanner’s pytest coverage and add a fixture with a lowercase justfile and README containing just build; run the relevant tests. Done means the justfile appears under setup scripts, its build command is counted, and Makefile-only output remains unchanged.

Written by the indexing model from the issue text.

Description

priority:low ready-for-dev

plugins/onboarding/skills/agent-readiness-report/scripts/scan_build_env.sh (at 599cc4dc95bf1f489dedaf9f722331b0cd71c52e) under-detects repositories that use just as their task runner, in two ways.

1. Only Justfile is checked, not justfile

Lines 21 and 31 test [ -f Justfile ]. just accepts justfile in any capitalization, and lowercase justfile is the name its documentation uses. On a case-sensitive filesystem (Linux, including most CI runners and containers), a repository with a justfile gets no "Setup scripts" entry and its justfile is not scanned for build commands. On macOS and Windows, whose filesystems usually ignore case, the same repository is detected, so the output depends on the OS.

2. The build-command grep has no just pattern

Line 23 matches make build, npm run build, cargo build, go build, gradle build, mvn.*package and bundle exec, but not just. A README or AGENTS.md that documents just build reports zero build command references.

Why it matters

The criteria accept a task runner (#41) and single-command setup (#65), and a justfile provides both. The scanner output is what points the agent at evidence, so on Linux the report can under-credit these repositories, or grade the same repository differently on Linux and macOS.

Repro (Linux)
mkdir /tmp/jf && cd /tmp/jf
printf 'build:\n\techo build\n' > justfile
printf 'Run `just build` to build.\n' > README.md
bash /path/to/scan_build_env.sh .

Expected: ./justfile under "-- Setup scripts --" and a build command reference for README.md. Actual (Linux), both sections empty:

-- Build commands --

-- Setup scripts --

-- Dev container --
Suggested fix
  • Lines 21 and 31: also check justfile (and .justfile, which just also accepts).
  • Line 23: add a just pattern, e.g. just [A-Za-z0-9_-]*build.

OpenHands AI triage

The following comments and acceptance criteria were added by the OpenHands AI agent.

Triage

Verified the report against plugins/onboarding/skills/agent-readiness-report/scripts/scan_build_env.sh: identical at the referenced commit (599cc4dc) and at current main (b98ac067). Lines 21 and 31 test only Justfile, and the line-23 grep has no just pattern; reproduced on Linux - a repo with a lowercase justfile and a README documenting just build shows empty "-- Build commands --" and "-- Setup scripts --". references/criteria.md feature 41 (Task runner) cites Justfile and feature 65 (Single-command dev setup) cites just setup, so the gaps affect reported scores, and detection currently depends on the host filesystem's case handling.

Scope: make scan_build_env.sh detect the just task-runner files in any capitalization (Justfile, justfile, .justfile) in both the setup-scripts and build-commands file lists, and add a just build-command pattern to the existing grep.

Non-goals: adding other task runners; changing the script's exit codes or argument handling; changing scoring methodology or references/criteria.md; scanning justfiles outside the repository root.

No prior user reports or production impact are on record and the reproduction is synthetic, so this is priority:low.

Acceptance Criteria
  • On a case-sensitive filesystem (e.g., Linux), running bash plugins/onboarding/skills/agent-readiness-report/scripts/scan_build_env.sh <fixture> on a repository whose root contains only lowercase justfile (no Justfile) prints ./justfile under -- Setup scripts --.
  • A root .justfile is likewise listed under -- Setup scripts --.
  • A README.md or AGENTS.md containing just build produces a nonzero "build command references" line for that file.
  • The build-commands scan also inspects the justfile variants it now detects (e.g., a justfile whose contents mention just build is counted).
  • A repository without just-related files keeps its previous output (e.g., a Makefile-only fixture still lists ./Makefile in both sections).
  • Automated coverage in the repository's pytest suite runs the scanner against a justfile fixture (lowercase file, README with just build) and passes.
Dominant language
Python
Stars
184
Forks
137
Avg merge
1d 16h
Merged PRs (30d)
60

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenHands/extensions

All issues in OpenHands/extensions

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.