Junie

https://junie.labs.jb.gg/docs
Admin
Junie is a coding agent by JetBrains that runs in JetBrains IDEs, in your terminal, or headless in...
Tokens:34,398
Snippets:480
Trust Score:9.9
Update:2 months ago
Show doc for...
Tokens:
Raw
### Example allowlist.json configuration

Source: https://junie.labs.jb.gg/docs/action-allowlist-junie-cli.html

A comprehensive example showing rule definitions for file editing, executables, MCP tools, and outside project access.

```json
{
  "defaultBehavior": "ask",
  "allowReadonlyCommands": true,
  "rules": {
    "fileEditing": {
      "rules": [
        {
          "prefix": "src/main/kotlin/", // The path is relative to the current project directory. For absolute paths, start with `/`.
          "action": "allow"
        }
      ]
    },
    "executables": {
      "rules": [
        {
          "prefix": "git",
          "action": "allow"
        },
        {
          "pattern": "grep **",
          "action": "allow"
        },
        {
          "pattern": "npm [iur]*",
          "action": "ask"
        }
      ]
    },
    "mcpTools": {
      "rules": [
        {
          "prefix": "github-server:",
          "action": "allow"
        }
      ]
    },
    "readOutsideProject": {
      "rules": [
        {
          "pattern": "/etc/**",
          "action": "ask"
        }
      ]
    }
  }
}
```

--------------------------------

### Example Demo Plan

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

A sample ordered list of user-visible milestones generated by Junie before VM initialization.

```text
1. Launch the app — main window shows the file tree.
2. Open Settings via the gear icon — Settings dialog appears.
3. Toggle "Dark theme" — UI re-renders in dark colors.
4. Close Settings — main window remains in dark mode.
```

--------------------------------

### Start Junie CLI

Source: https://junie.labs.jb.gg/docs/byok-openrouter.html

Initializes the Junie application within the current project directory.

```bash
junie
```

--------------------------------

### Start Junie in a project

Source: https://junie.labs.jb.gg/docs/junie-cli.html

Navigate to the project directory and launch the Junie CLI interface.

```bash
cd /path/to/your/project
```

```shell
junie
```

--------------------------------

### Install an extension via CLI

Source: https://junie.labs.jb.gg/docs/junie-cli-extensions.html

Use this command to install a specific extension by name directly from the command line.

```bash
/extensions install <extension-name>
```

--------------------------------

### Extensions Configuration Format

Source: https://junie.labs.jb.gg/docs/junie-cli-extensions.html

Example of the JSON structure used in extensions.json files to map marketplace identifiers to installed extensions and their source definitions.

```json
{
  "github-JetBrains-junie-extensions": { "extensions": ["context7"] },
  "github-myorg-myrepo": {
    "url": "https://github.com/myorg/myrepo",
    "source": { "type": "git", "url": "https://github.com/myorg/myrepo" },
    "extensions": ["my-ext"]
  },
  "local-my-dir-abc12345": {
    "source": { "type": "local", "path": "/Users/me/my-marketplace" },
    "extensions": ["my-local-ext"]
  },
  "url-github-anthropics-knowledge-work-plugins-xxxxxxxxxx": {
    "source": { "type": "url", "url": "https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/.claude-plugin/marketplace.json" },
    "extensions": ["some-ext"]
  }
}
```

--------------------------------

### Install Junie Local via CLI

Source: https://junie.labs.jb.gg/docs/junie-local.html

Downloads and executes the Junie Local installer script. Ensure the script is downloaded locally rather than piped directly to shell to allow for required user input.

```bash
curl -fsSL https://junie.jetbrains.com/install-local.sh -o /tmp/junie-local-install.sh && sh /tmp/junie-local-install.sh
```

--------------------------------

### Start Junie CLI in Plan mode

Source: https://junie.labs.jb.gg/docs/junie-cli-plan-mode.html

Use command-line flags to initialize the CLI in Plan mode, with an optional auto-submitted prompt.

```bash
junie --plan
junie --prompt "Refactor the commands module" --plan
```

--------------------------------

### Verify Junie CLI Installation

Source: https://junie.labs.jb.gg/docs/junie-cli-eap.html

Check the installed version of the Junie CLI to confirm the installation was successful.

```bash
junie --version
```

--------------------------------

### Install Junie CLI EAP

Source: https://junie.labs.jb.gg/docs/junie-cli-eap.html

Use these commands to install the pre-release version of the Junie CLI on your system.

```bash
curl -fsSL https://junie.jetbrains.com/install-eap.sh | bash
```

```powershell
powershell -NoProfile -ExecutionPolicy Bypass -Command "iex (irm 'https://junie.jetbrains.com/install-eap.ps1')"
```

--------------------------------

### Configure a Bedrock Proxy

Source: https://junie.labs.jb.gg/docs/custom-proxies.html

Example configuration for a Bedrock proxy, including the required available-models field and optional authorization headers.

```json
{
  "proxies": [
    {
      "name": "corp-bedrock",
      "kind": "Bedrock",
      "api-url": "https://bedrock-gateway.example",
      "available-models": ["anthropic-claude-4-6-sonnet", "anthropic-claude-4-8-opus"],
      "headers": [
        "Authorization: Bearer <your-token>"
      ]
    }
  ],
  "provider": "corp-bedrock",
  "model": "sonnet"
}
```

--------------------------------

### Configure .aiignore file

Source: https://junie.labs.jb.gg/docs/junie-ide-plugin.html

Example of an .aiignore file structure used to restrict Junie's access to specific project files.

```text
.aiignore
 {...}
```

--------------------------------

### Prompting in Junie CLI

Source: https://junie.labs.jb.gg/docs/junie-cli.html

Example of a natural language prompt provided to the interactive CLI.

```text
> give me an overview of this codebase
```

--------------------------------

### Invoke a custom slash command with arguments

Source: https://junie.labs.jb.gg/docs/custom-slash-commands.html

Example of how to trigger a custom command named 'explain' by providing a value for the '$file' argument.

```text
/explain file=src/main.kt
```

--------------------------------

### Rule precedence example

Source: https://junie.labs.jb.gg/docs/action-allowlist-junie-cli.html

Demonstrates how rule order affects matching, where specific patterns take precedence over general prefixes.

```json
{
     "rules": [
       {
         "pattern": "npm install *",
         "action": "ask"
       },
       {
         "prefix": "npm",
         "action": "allow"
       }
     ]
   }
```

--------------------------------

### Define a simple subagent

Source: https://junie.labs.jb.gg/docs/junie-cli-subagents.html

A basic example of a subagent configuration file for a changelog assistant.

```yaml
---
name: "changelog"
description: "Write a changelog entry for a PR"
---

You are a changelog assistant.

Given the PR title and description, produce a short changelog entry.
```

--------------------------------

### Run Junie CLI in headless mode

Source: https://junie.labs.jb.gg/docs/junie-cli.html

Commands to install the CLI, authenticate, and execute tasks or code reviews in non-interactive environments.

```bash
# Install Junie CLI
curl -fsSL https://junie.jetbrains.com/install.sh | bash

# Authenticate and run a task
junie --auth="$JUNIE_API_KEY" "Fix any failing tests"

# Run a code review of the latest commit
junie --auth="$JUNIE_API_KEY" --review
```

--------------------------------

### Configure Junie with Provider API Keys

Source: https://junie.labs.jb.gg/docs/junie-on-github.html

Examples of providing specific LLM provider keys for Bring-Your-Own-Key (BYOK) authentication. Provide either the Junie API key or one of the provider keys, but not both.

```yaml
- uses: JetBrains/junie-github-action@v1
  with:
    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
```

```yaml
- uses: JetBrains/junie-github-action@v1
  with:
    openrouter_api_key: ${{ secrets.OPENROUTER_API_KEY }}
```

--------------------------------

### Install Stable Junie CLI

Source: https://junie.labs.jb.gg/docs/junie-cli-eap.html

Reinstall the stable version of the Junie CLI after removing the EAP launcher.

```bash
curl -fsSL https://junie.jetbrains.com/install.sh | bash
```

```powershell
powershell -NoProfile -ExecutionPolicy Bypass -Command "iex (irm 'https://junie.jetbrains.com/install.ps1')"
```

--------------------------------

### Start Remote Mode

Source: https://junie.labs.jb.gg/docs/junie-cli-remote-mode.html

Initiate a remote session by executing the slash command within the Junie CLI terminal.

```text
> /remote
```

--------------------------------

### Define Demo Configuration

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

Create a .junie/demo.md file to specify the target VM and define build and launch commands.

```markdown
# My web app

vm: node-vm

## Build inside the VM
    npm install && npm run build

## Launch
    npm run start &
    # ready when http://localhost:3000 responds 200
```

```markdown
# My Python app

vm: python-vm

## Build inside the VM
    pip install -r requirements.txt

## Launch
    python app.py &
    # ready when http://localhost:5000 responds 200
```

--------------------------------

### Initiate Demo Command

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

Execute the demo command to open the interactive picker interface.

```bash
/demo
```

--------------------------------

### View Junie CLI Help

Source: https://junie.labs.jb.gg/docs/junie-headless.html

Display all available command-line options.

```bash
junie --help
```

--------------------------------

### Demo a Feature in a Fresh Repo

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

Initiate a demo by navigating to the text field and providing specific instructions for the agent to follow.

```text
> /demo
…press ↓ past the last scope to reach the text field
> open the project, run the example notebook, show the chart it produces
```

--------------------------------

### Connect to LiteLLM via CLI

Source: https://junie.labs.jb.gg/docs/custom-llm-litellm.html

Use CLI flags to specify the LiteLLM proxy URL and API key during startup.

```bash
junie --litellm-url http://localhost:4000 --litellm-api-key sk-1234
```

```bash
junie --litellm-url http://localhost:4000 --litellm-api-key sk-1234 --model my-coder-model
```

--------------------------------

### Configure System Options

Source: https://junie.labs.jb.gg/docs/parameters.html

Manage IDE integration, cache directories, and system-level settings.

```bash
junie --acp true
```

```bash
junie --cache-dir "/tmp/junie-cache"
```

```bash
junie --help
```

```bash
junie --timeout 30000
```

```bash
junie --version
```

--------------------------------

### Define a quick-start checklist in AGENTS.md

Source: https://junie.labs.jb.gg/docs/guidelines-and-memory.html

Use a bulleted list to define critical pre-task requirements for the agent.

```markdown
# A short bullet list of the most critical rules the agent must follow before doing anything

- [ ] Read this file and `README.md` before acting.
- [ ] Update `CHANGELOG.md` for user-facing changes.
```

--------------------------------

### Start a new Junie session

Source: https://junie.labs.jb.gg/docs/junie-cli-worktrees.html

Initiates a new interactive session while keeping the current one active in the background.

```text
/new update the tests for the payment flow
```

--------------------------------

### Configure Core CLI Options

Source: https://junie.labs.jb.gg/docs/parameters.html

Manage input/output formats, file paths, and session settings.

```bash
junie --input-format json
```

```bash
junie --output-format text
```

```bash
junie --json-output-file ./output.json
```

```bash
junie --guidelines-filename "guidelines_ci.md"
```

```bash
junie --model sonnet "my task"
```

```bash
junie --project ./path/to/project
```

```bash
junie --session-id session-251209-172932-1ze8
```

```bash
junie --skip-update-check "my task"
```

```bash
junie --prompt "Fix the bug"
```

```bash
junie --plan
```

```bash
junie --task "task in plain English"
```

--------------------------------

### Define Custom VM Dockerfiles

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

Create a Dockerfile in .junie/vms/<your-vm>/ to specify runtime dependencies. The base image registry.jetbrains.team/p/junie-cli/containers/demo-base:2 must be used.

```dockerfile
# .junie/vms/node-vm/Dockerfile
FROM registry.jetbrains.team/p/junie-cli/containers/demo-base:2
RUN apt-get update && apt-get install -y --no-install-recommends nodejs npm
```

```dockerfile
# .junie/vms/python-vm/Dockerfile
FROM registry.jetbrains.team/p/junie-cli/containers/demo-base:2
RUN apt-get update && apt-get install -y --no-install-recommends python3 python3-pip
```

--------------------------------

### Select a custom model via command line

Source: https://junie.labs.jb.gg/docs/custom-llm-models.html

Use the --model flag followed by the custom: prefix and the profile ID to specify a custom model.

```bash
junie --model custom:local-ollama
```

--------------------------------

### Define Test Pattern Instructions

Source: https://junie.labs.jb.gg/docs/agent-skills.html

Use these specific instructions to guide the agent in writing tests using the AAA pattern.

```text
Use the AAA pattern (Arrange, Act, Assert).
One assertion concept per test.
Use fakes instead of mocking libraries.
```

--------------------------------

### Configure VM Mounts

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

Define additional bind mounts in .junie/vms/<your-vm>/mounts using the format <hostPath>:<guestPath>[:ro|:rw].

```text
# <hostPath>:<guestPath>[:ro|:rw]
# $HOME and ${HOME} are expanded from the environment.
# Lines starting with # are ignored.
$HOME/.config/my-app:/root/.config/my-app:ro
/tmp/fixtures:/workspace/fixtures
```

--------------------------------

### Reference Project Files for Skills

Source: https://junie.labs.jb.gg/docs/agent-skills.html

Direct the agent to specific files to serve as implementation references.

```text
See `src/test/kotlin/com/example/MyServiceTest.kt` for a reference
test implementation.
```

--------------------------------

### Define a complex subagent with metadata

Source: https://junie.labs.jb.gg/docs/junie-cli-subagents.html

An example demonstrating advanced frontmatter fields including tools, model selection, and reasoning levels.

```yaml
---
description: "Review a change and propose a safe patch"
name: "code-review-helper"
tools: ["Read", "Grep", "Edit"]
disallowedTools: ["Bash", "WebSearch"]
mcpServers: ["github"]
model: "sonnet"
reasoningLevel: "high"
maxTurns: 20
skills: ["kotlin", "writerside"]
allowPromptArgument: true
---

You are a careful code reviewer.

Context:

- File: $path
- Focus area: $focus

Tasks:

1) Explain the issue concisely.
2) Propose a minimal fix.
3) If edits are needed, prepare a small patch.

If you need additional context, ask for it.
```

--------------------------------

### Load additional configuration files

Source: https://junie.labs.jb.gg/docs/junie-cli-configuration.html

Use the --config-location flag to specify multiple custom configuration file paths.

```bash
junie \
  --config-location /opt/company/junie/config.json \
  --config-location ./configs/junie.local.json
```

--------------------------------

### Configure model and skill discovery

Source: https://junie.labs.jb.gg/docs/parameters.html

Manage search paths for custom models, skills, commands, and agents.

```bash
junie --model-location ./.junie/models
```

```bash
junie --model-default-locations false
```

```bash
junie --skill-location ./shared-skills
```

```bash
junie --skill-default-locations false
```

```bash
junie --command-location ./shared-commands
```

```bash
junie --command-default-locations false
```

```bash
junie --agent-location ./shared-agents
```

```bash
junie --agent-default-location false
```

--------------------------------

### Custom Demo Descriptions

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

Provide specific natural language instructions in the picker's free-form field to guide the demo agent.

```text
show the new dark-theme toggle in Settings
open the search dialog and find 'TODO'
log in as user@example.com and open the profile page
```

--------------------------------

### Project Directory Structure for Multiple VMs

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

Organize multiple VM templates by placing subdirectories under .junie/vms/, each containing its own Dockerfile and optional mounts file.

```text
.junie/
├── demo.md
└── vms/
    ├── backend-vm/
    │   ├── Dockerfile
    │   └── mounts
    ├── frontend-vm/
    │   └── Dockerfile
    └── cli-vm/
        └── Dockerfile
```

--------------------------------

### Configure GitHub Actions for code review

Source: https://junie.labs.jb.gg/docs/automated-code-reviews.html

Example YAML configuration for a GitHub Actions workflow that triggers Junie on pull request events.

```yaml
# .github/workflows/code-review.yml
name: Code Review

on:
  pull_request:
    types: [opened, synchronize]

jobs:
  review:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
      issues: write
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 1

      - uses: JetBrains/junie-github-action@v0
        with:
          junie_api_key: ${{ secrets.JUNIE_API_KEY }}
          # Update the same comment on subsequent Junie runs instead of adding new comments
          use_single_comment: true
          # Alternatively, write your custom review instructions in the prompt field
          # instead of using the built-in "code-review" value
          prompt: "code-review"
```

--------------------------------

### Submit a prompt in Plan mode

Source: https://junie.labs.jb.gg/docs/junie-cli-plan-mode.html

Use the /plan slash command to toggle Plan mode and optionally submit a prompt immediately.

```text
> /plan refactor commands
```

--------------------------------

### Import skills from Git repositories

Source: https://junie.labs.jb.gg/docs/agent-skills.html

Commands to clone a repository and copy specific skills into local or global skill directories.

```bash
# Clone the repo (or download just the skill folder)
git clone https://github.com/JetBrains/skills.git /tmp/junie-skills

# Copy a specific skill to your project
cp -r /tmp/junie-skills/spring-kotlin-code-review .junie/skills/

# Or copy to your global skills for use across all projects
cp -r /tmp/junie-skills/spring-kotlin-code-review ~/.junie/skills/

# Clean up
rm -rf /tmp/junie-skills
```

```powershell
# Clone the repo (or download just the skill folder)
git clone https://github.com/JetBrains/skills.git $env:TEMP\junie-skills

# Copy a specific skill to your project
Copy-Item -Recurse -Force $env:TEMP\junie-skills\spring-kotlin-code-review .junie\skills\

# Or copy to your global skills for use across all projects
Copy-Item -Recurse -Force $env:TEMP\junie-skills\spring-kotlin-code-review "$env:USERPROFILE\.junie\skills\"

# Clean up
Remove-Item -Recurse -Force $env:TEMP\junie-skills
```

--------------------------------

### Execute Junie CLI in Headless Mode

Source: https://junie.labs.jb.gg/docs/junie-headless.html

Run a prompt using an authentication token provided via environment variable.

```bash
junie --auth="$JUNIE_API_KEY" "Review and fix any code quality issues in the latest commit"
```

--------------------------------

### Verify a Fix with /demo

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

Use the /demo command after making changes to verify bug fixes by selecting the appropriate session scope.

```text
> fix the bug where the search box loses focus after typing one character
…Junie edits files, runs tests…
> /demo
…pick "Changes from this session" (or "Uncommitted changes")
```

--------------------------------

### Feature-Specific Demo Request

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

Specify an existing feature by name to have the agent resolve the navigation path and demonstrate it.

```text
the file-tree drag-and-drop in the sidebar
```

--------------------------------

### View the built-in code review prompt

Source: https://junie.labs.jb.gg/docs/automated-code-reviews.html

The default instructions used by Junie to analyze pull request diffs and provide feedback.

```text
Your task is to:

1. Get the Pull Request diff using `${diffCommand}`.
2. Review this diff according to the criteria below.
3. For each specific finding, use the 'post_inline_review_comment' tool (if available) to provide feedback directly on the code.
4. Once all findings are posted (or if the tool is unavailable), call the 'answer' tool with your review as a bullet point list in the 'full_answer' field.

Additional instructions:

1. Review ONLY the changed lines against the Core Review Areas below, prioritizing repository style/guidelines adherence and avoiding overcomplication.
2. You may open files or search the project to understand context. Do NOT run tests, build, or make any modifications.
3. Do NOT call 'submit'.

### Core Review Areas

1. **Adherence with this repository style and guidelines**

- Naming, formatting, and package structure consistency with existing code and modules.
- Reuse of existing utilities/patterns; avoiding introduction of new dependencies.

2. **Avoiding overcomplications**

- Avoid new abstractions, frameworks, premature generalization, or unnecessarily complicated solutions.
- Avoid touching of unrelated files.
- Avoid unnecessary indirection (wrappers, flags, configuration) and ensure straightforward control flow.
- Do not allow duplicate logic.

### If obviously applicable to the CHANGED lines only

- Security: newly introduced unsafe input handling, command execution, or data exposure.
- Performance: unnecessary allocations/loops/heavy work on UI thread introduced by the change.
- Error handling: swallowing exceptions or deviating from existing error-handling patterns.

### Output Format

- If the 'post_inline_review_comment' tool is available, use it for each specific finding.
- **Use the tool parameters correctly**:
    - `filePath`: The relative path to the file.
    - `lineNumber`: The line (or end of range) where the comment applies.
    - `startLineNumber`: Use this for multi-line comments to cover a range.
    - `commentBody`: Your explanation. Use the ```suggestion syntax here for code changes.
- Once all inline comments are posted, call the 'answer' tool with your review as a bullet point list in the 'full_answer' field.
- If the tool is NOT available, use the fallback format in 'full_answer' only: -`File.ts:Line: Comment`.
- Comment ONLY on lines added in this diff (`+` lines). Do not comment on pre-existing code.
- Keep it concise (15–25 words per comment). No praise, questions, or speculation; omit low-impact nits.
- If unsure whether a comment applies, omit it. If no feedback is warranted, answer `LGTM` only.
- For small changes, max 3 comments; medium 6–8; large 8–12.
```

--------------------------------

### Manage Marketplaces via CLI

Source: https://junie.labs.jb.gg/docs/junie-cli-extensions.html

Commands to add or remove marketplaces directly from the command line interface.

```text
/extensions marketplace add <spec>
/extensions marketplace remove
```

--------------------------------

### Run Junie with custom configuration

Source: https://junie.labs.jb.gg/docs/custom-proxies.html

Execute the Junie CLI using the --config-location flag to point to your custom configuration file.

```bash
junie --config-location="/path/to/my-config.json"
```

```bash
junie --config-location="/path/to/my-config.json" --model sonnet
```

--------------------------------

### Define local development commands in AGENTS.md

Source: https://junie.labs.jb.gg/docs/guidelines-and-memory.html

Use a table to document project-specific commands for common development tasks.

```markdown
# A table or list of project-specific commands for install, lint, test, build, and span dev server

| Task                 | Command        |
|----------------------|----------------|
| Install dependencies | `pnpm install` |
| Start dev server     | `pnpm dev`     |
| Run unit tests       | `pnpm test`    |
```

--------------------------------

### Compare Before and After Behavior

Source: https://junie.labs.jb.gg/docs/junie-cli-demo.html

Demonstrate behavioral changes by instructing the agent to show both the old and new states of a feature.

```text
> /demo
…press ↓ past the last scope to reach the text field
> show the old behavior, then the new behavior of the export button
```

--------------------------------

### Configure Junie CLI file locations

Source: https://junie.labs.jb.gg/docs/parameters.html

Specify custom configuration file paths or toggle default location loading.

```bash
junie --config-location ./configs/junie.json
```

```bash
junie --config-default-locations false
```

--------------------------------

### Configure a GitHub MCP server with environment file

Source: https://junie.labs.jb.gg/docs/junie-ide-plugin.html

Uses an external .env file to securely load environment variables for the GitHub MCP server configuration.

```json
{
    "mcpServers": {
        "github": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "--env-file",
                "~/.env.mcp",
                "ghcr.io/github/github-mcp-server"
            ]
        }
    }
}
```

--------------------------------

### Define UI and architecture guidelines

Source: https://junie.labs.jb.gg/docs/guidelines-and-memory.html

Set standards for design system usage and architectural patterns.

```markdown
# UI and architecture guidelines

- Use existing design system components.
- Avoid inline styles.
- Follow current domain boundaries.
- Prefer extending existing services.
```

--------------------------------

### Configure Provider API Keys

Source: https://junie.labs.jb.gg/docs/parameters.html

Authenticate directly with specific LLM providers using their respective API keys.

```bash
junie --anthropic-api-key sk-...
```

```bash
junie --google-api-key AI...
```

```bash
junie --grok-api-key sk-...
```

```bash
junie --openai-api-key sk-...
```

```bash
junie --openrouter-api-key sk-...
```

--------------------------------

### Authenticate with Junie CLI

Source: https://junie.labs.jb.gg/docs/parameters.html

Use the auth flag to provide your API key or license key for authentication.

```bash
junie --auth perm-...
```

```bash
junie --auth-license ...
```

--------------------------------

### Define testing and contribution guidelines

Source: https://junie.labs.jb.gg/docs/guidelines-and-memory.html

Outline expectations for testing and code maintenance.

```markdown
# Testing and contribution

- Add unit tests for new business logic.
- Keep changes minimal and avoid large refactors in feature tasks.
- Do not rename files without a valid technical reason.
```

--------------------------------

### Format SKILL.md file

Source: https://junie.labs.jb.gg/docs/agent-skills.html

The standard template for SKILL.md files, requiring YAML frontmatter for identification and Markdown for instructions.

```markdown
---
name: my-skill-name
description: A short description of what this skill provides
---

# My Skill Name

Use this skill when [describe when Junie should use this skill].

## Key Principles
- Principle 1
- Principle 2

## Guidelines
- Guideline 1
- Guideline 2

## Examples

[Include code examples, patterns, or references to project files]

## Checklist

See `checklists/review.md` for a detailed checklist.
```
Tokens:
Raw