cli-just
Imported from paulrberg/agent-skills/skills/cli-just.
Install
npx skills add https://github.com/PaulRBerg/agent-skills/tree/main/skills/cli-just
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install paulrberg-agent-skills@llmmart
git clone https://github.com/PaulRBerg/agent-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole paulrberg/agent-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Just Command Runner
Create readable task automation that matches the repository's installed Just version and existing justfile conventions.
Defaults
Inspect
just --version, the existing justfile/module tree, andjust --listbefore editing. Installed capabilities and existing syntax are authoritative over this skill's examples.Preserve bespoke formatting. Do not rewrite a justfile with
just --fmt. Usejust --fmt --checkonly when the repository explicitly treats the built-in formatter as authoritative.just --dumpis inspection output, not a formatting source.Define multi-item string sequences one item per line with a parenthesized concatenation. Keep a trailing separator in every non-final item. Do not combine them into one long string. Triple-quoted strings are for values whose newlines are semantic, not visual wrapping. For example:
check-steps := ( "event-class-coverage " + "orphan-disposal " + "price-coverage" )When creating a new standalone justfile, use the user's section-banner style. Existing repository organization overrides that style.
Workflow
Determine the requested recipe behavior, inputs, outputs, cwd, shell, environment, dependencies, and success condition.
Use the installed manual (
just --help,just --man, or https://just.systems/man/en/) for version-sensitive syntax. Read only the task-specific reference:Task Reference Recipes, parameters, dependencies, cache, executable checks, echo rules references/recipes.mdSettings, dotenv, lists, modules references/settings.mdExpressions, functions, constants references/syntax.mdShell or script recipes, macOS Bash constraints references/inline-scripts.mdCheck/write, status, aliases, organization references/patterns.mdMake the smallest recipe or setting change. Do not enable unstable features unless the requested design needs them and the installed version supports them.
Validate parsing with
just --listorjust --summary. Then execute the narrowest safe recipe path. For state-changing recipes, use an existing dry-run/check mode or inspect the expanded command first.
Opinionated Organization
For a new standalone file, prefer dependency declarations, constants, public recipes, checks, then private helpers. Use
set default-list := true when no single default action makes sense and the installed version supports it. Example
starting points are in examples/standalone.just and examples/devkit.just. Load one only when creating that shape.
Completion requires a parsable justfile, the requested recipe behavior, and execution or dry-run evidence appropriate to
its side effects. Finish with ### ✅ Just workflow ready, a compact recipe/alias/purpose table when several entries
changed, and ### 🧪 Verification with exact commands and outcomes. Keep confirmation prompts, recipe data output,
compiler output, and just --list output undecorated. Preserve the repository's own banner vocabulary.
Files (agent-skills)
-
agents
-
openai.yaml 42 B
Loading…
-
-
examples
-
devkit.just 1.1 KB · in bundle
-
standalone.just 4.3 KB · in bundle
-
-
references
-
inline-scripts.md 1.4 KB
Loading… -
patterns.md 754 B
Loading… -
recipes.md 2 KB
Loading… -
settings.md 1.3 KB
Loading… -
syntax.md 722 B
Loading… -
version.txt 7 B
Loading…
-
-
SKILL.md 3.6 KB
--- name: cli-just user-invocable: false description: "Use for just/justfile task automation: create justfiles, write recipes, configure settings, add modules/attributes, or set up command-runner workflows." --- # Just Command Runner Create readable task automation that matches the repository's installed Just version and existing justfile conventions. ## Defaults - Inspect `just --version`, the existing justfile/module tree, and `just --list` before editing. Installed capabilities and existing syntax are authoritative over this skill's examples. - Preserve bespoke formatting. Do not rewrite a justfile with `just --fmt`. Use `just --fmt --check` only when the repository explicitly treats the built-in formatter as authoritative. `just --dump` is inspection output, not a formatting source. - Define multi-item string sequences one item per line with a parenthesized concatenation. Keep a trailing separator in every non-final item. Do not combine them into one long string. Triple-quoted strings are for values whose newlines are semantic, not visual wrapping. For example: ```just check-steps := ( "event-class-coverage " + "orphan-disposal " + "price-coverage" ) ``` - When creating a new standalone justfile, use the user's section-banner style. Existing repository organization overrides that style. ## Workflow 1. Determine the requested recipe behavior, inputs, outputs, cwd, shell, environment, dependencies, and success condition. 2. Use the installed manual (`just --help`, `just --man`, or <https://just.systems/man/en/>) for version-sensitive syntax. Read only the task-specific reference: | Task | Reference | | ----------------------------------------------------------------------- | ------------------------------ | | Recipes, parameters, dependencies, cache, executable checks, echo rules | `references/recipes.md` | | Settings, dotenv, lists, modules | `references/settings.md` | | Expressions, functions, constants | `references/syntax.md` | | Shell or script recipes, macOS Bash constraints | `references/inline-scripts.md` | | Check/write, status, aliases, organization | `references/patterns.md` | 3. Make the smallest recipe or setting change. Do not enable unstable features unless the requested design needs them and the installed version supports them. 4. Validate parsing with `just --list` or `just --summary`. Then execute the narrowest safe recipe path. For state-changing recipes, use an existing dry-run/check mode or inspect the expanded command first. ## Opinionated Organization For a new standalone file, prefer dependency declarations, constants, public recipes, checks, then private helpers. Use `set default-list := true` when no single default action makes sense and the installed version supports it. Example starting points are in `examples/standalone.just` and `examples/devkit.just`. Load one only when creating that shape. Completion requires a parsable justfile, the requested recipe behavior, and execution or dry-run evidence appropriate to its side effects. Finish with `### ✅ Just workflow ready`, a compact recipe/alias/purpose table when several entries changed, and `### 🧪 Verification` with exact commands and outcomes. Keep confirmation prompts, recipe data output, compiler output, and `just --list` output undecorated. Preserve the repository's own banner vocabulary.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.