projj

Manage git repositories with directory conventions.

Runssource: GitHubRustMITcommit 1083f8a45206

Rust, MIT licensed. The project labels itself: hooks, project management, repository and repository management.

projj runs. An Argusic agent installed it in 20 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

projj compiles from source, passes all 124 tests, and the installed binary correctly lists repos, finds them by keyword, and runs both inline commands and named tasks.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
284
forks
44
open issues
5
watchers
5
size
0 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
20 minutes
Cold machine to finish
3 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
cargo test exited 0, 124 passed (93 unit + 27 CLI + 4 interactive); projj --version returned 'projj 0.0.0-dev'; projj list/find/run all produced correct output with real config and repo fixtures
Model tokens used
97,631
Exact commit tested
1083f8a45206
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Everything is solid. Here's the summary:
**Install**: Installed Rust via rustup (stable 1.99.1), built with `cargo build`, and installed wit…
**Tests**: All 124 tests pass — 93 unit tests, 27 CLI integration tests, and 4 PTY-based interactiv…
**Binary**: `projj --version` reports `projj 0.0.0-dev`. Verified real behavior: `list`, `find`, `r…
**Errors**: None encountered.
tokens used
97,631
Everything is solid. Here's the summary:
**Install**: Installed Rust via rustup (stable 1.99.1), built with `cargo build`, and installed wit…
**Tests**: All 124 tests pass — 93 unit tests, 27 CLI integration tests, and 4 PTY-based interactiv…
**Binary**: `projj --version` reports `projj 0.0.0-dev`. Verified real behavior: `list`, `find`, `r…
**Errors**: None encountered.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 20 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • Following its own README: the documented path worked with nothing to fix.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

hooksproject-managementrepositoryrepository-management

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/projj.svg)](https://argusic.com/subject/projj)

Questions

Does projj run?
Yes. projj runs. Argusic installed and launched it on a clean machine in 20 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test projj?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1083f8a45206. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test projj?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does projj take to install?
20 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does projj need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing projj?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for projj?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion