القائمة
Interface with the Google Jules CLI to delegate asynchronous coding tasks. Use this tool to execute a specific plan, start a background session, or retrieve results from a remote Jules agent.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | jules-cli |
| description | Interface with the Google Jules CLI to delegate asynchronous coding tasks. Use this tool to execute a specific plan, start a background session, or retrieve results from a remote Jules agent. |
To execute the jules command-line tool for delegating long-running or complex coding tasks to a remote agent session. This skill handles session creation, status monitoring, and result retrieval.
jules remote new--session "<prompt>": The detailed instruction or plan you want Jules to execute.--repo .: Specifies the current directory as the target repository.jules without arguments (this opens a TUI).jules remote <action>.jules remote list --session to check the status of running tasks.jules remote pull --session <ID> to apply the changes (PR/Branch) locally once the task is complete.| Action | Command Pattern |
|---|---|
| Start New Session | jules remote new --repo . --session "<Your Plan>" |
| List Sessions | jules remote list --session |
| Pull Results | jules remote pull --session <Session_ID> |
| Check Version | jules version |
User: "Here is the refactoring plan for the auth module. Run it with Jules." Agent Execution:
jules remote new --repo . --session "Refactor src/auth.ts to use the Singleton pattern. Update all import references in src/routes/ to match the new class structure. Run tests to verify."
Execute the technical plan for a feature using bounded, task-by-task execution. Acts as the "Goldfish", relying on strict constraints from the "Elephant" (spec.md).
Define requirements, specifications, architecture, and step-by-step task plans for a new feature or modification. Orchestrates the creation of the Elephant (spec.md) and Goldfish Checklist (plan.md).
Establish a project governance document (constitution.md) with immutable architectural articles that all Bolts inherit. Run once per project before bolt-roadmap.
Investigate and document technology choices before architecture is locked. Invoked from bolt-intent Phase 2 when new technology decisions are required. Produces research.md. Optional — skip with documented reason when Bolt extends an established pattern.
Structured post-Bolt retrospective that captures process improvements, proposes constitution amendments, and updates bolt-* skills. Targets the development process — not the project. Distinct from bolt-synthesis.
Create a comprehensive strategic roadmap and diagram for the project by decomposing high-level goals into atomic, sequential/parallel bolts.