junie-cli

Delegate multi-step repository tasks to a Junie CLI subagent with shared-state handoff.

5|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/amirkiarafiei/subagent-cli-skills --skill junie-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: junie-cli
Source: https://github.com/amirkiarafiei/subagent-cli-skills/tree/main/skills/junie-cli
Command: npx skills add https://github.com/amirkiarafiei/subagent-cli-skills --skill junie-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Junie CLI helps you handle large, multi-step repository tasks without overloading your main agent’s context window, reducing the cost and complexity of staying in one chat thread.

Core Features & Use Cases

  • Subagent-style delegation: Runs a separate long-horizon pass (with a context handoff) for code reviews, refactors, and broad implementation work.
  • Specialized collaboration modes: Supports dedicated workflows for code review and git merge/rebase conflict resolution.
  • Alignment via shared state: Lets you include the full goal, prior decisions, scope, constraints, and verification steps so an isolated session stays consistent with the main thread.

Quick Start

Use Junie CLI to review your changes by asking your orchestrator to run the junie-cli skill and pass the full goal, scope (paths), the specific concerns, and the verification command you want Junie to run before returning.

Frequently Asked Questions about junie-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate large refactoring or code review tasks without overloading my agent context window?

Subagent delegation offloads long-horizon refactoring and code review tasks to a separate CLI session using an explicit shared-state handoff, preserving your main agent's context window while maintaining alignment through passed goals, scope, and constraints.

Can I automate git merge and rebase conflict resolution through an agentic workflow?

Yes, automated git merge and rebase conflict resolution is supported through specialized collaboration modes that ensure verification and safe reconciliation of results within a delegated subagent session.

What's the best way to run isolated CI/CD implementation tasks while keeping prior decisions aligned?

Pass the full goal, prior decisions, scope, constraints, and verification commands as shared state to an isolated subagent session, ensuring CI/CD implementation stays consistent with your main thread without context overload.

Do I need programmatic authentication to use repository automation for multi-step tasks?

Yes, programmatic usage with mandatory authentication and explicit model selection is required to execute repository automation tasks, ensuring controlled output formatting and safe review or merge operations.

Does this subagent delegation approach work for both code generation and documentation tasks?

Subagent delegation applies to code reviews, refactors, CI/CD-oriented implementation, and documentation tasks, supporting broad repository work through controlled output formatting and optional review modes.

Why does my main agent lose alignment when running long multi-step repository work in one thread?

Long multi-step repository work in a single thread overloads the context window and increases complexity, which the shared-state handoff mechanism solves by isolating the work while passing goals and constraints to maintain alignment.