> ## Documentation Index
> Fetch the complete documentation index at: https://lightsage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Pull actionables into your agent

> Copy a prompt that has your coding agent pull your Lightsage tasks and opportunities and ship fixes for them.

Copy one of the prompts below into your coding agent to pull your Lightsage tasks and opportunities and fix them in your repository.

## Before you start

* A Lightsage API key from **Settings > API Keys**.
* [Lightsage MCP](/docs/mcp-reference) connected to your agent, or the [Lightsage CLI](/docs/cli-reference) installed and authenticated.
* The agent running in the repository or docs site the work points at.

Both prompts are deliberately general so you can reuse them. Adjust the inputs, the item count, and the review rules to match how your team works.

## The prompt

<CodeGroup>
  ```text Lightsage MCP theme={null}
  Pull my Lightsage tasks and opportunities, then fix the top 3.

  Use the Lightsage MCP server. Discover the available tools first, then gather:
  - today's daily task queue, active items only
  - ranked opportunities from the last 30 days

  Tasks and opportunities both include an execution prompt with the context needed to
  address them. Read it before you start changing anything.

  Both are already ranked and carry score, effort, and priority. Use those to pick the
  top 3 overall. Work them one at a time. For each one:
  - restate the user-visible problem in your own words
  - find the repo files or docs pages responsible
  - make the smallest change that fixes it
  - follow the conventions already used in the surrounding files
  - open one pull request per item

  Once a pull request is open, use Lightsage MCP to move the daily task to in_progress.

  Do not mark anything done until the pull request merges.
  Report what you changed and the pull request links when finished.
  ```

  ```text Lightsage CLI theme={null}
  Pull my Lightsage tasks and opportunities, then fix the top 3.

  Use the Lightsage CLI. Run `lightsage --help` to discover the command surface, then gather:
  - today's daily task queue, active items only
  - ranked opportunities from the last 30 days

  Request JSON output so you can parse the results.

  Tasks and opportunities both include an execution prompt with the context needed to
  address them. Read it before you start changing anything.

  Both are already ranked and carry score, effort, and priority. Use those to pick the
  top 3 overall. Work them one at a time. For each one:
  - restate the user-visible problem in your own words
  - find the repo files or docs pages responsible
  - make the smallest change that fixes it
  - follow the conventions already used in the surrounding files
  - open one pull request per item

  Once a pull request is open, use the CLI to move the daily task to in_progress.

  Do not mark anything done until the pull request merges.
  Report what you changed and the pull request links when finished.
  ```
</CodeGroup>

## Related docs

<CardGroup cols={2}>
  <Card title="Lightsage MCP" icon="plug" href="/docs/mcp-reference">
    Connect supported coding agents so they can fetch Lightsage context directly.
  </Card>

  <Card title="CLI Reference" icon="terminal" href="/docs/cli-reference">
    Install the CLI and see the full command surface.
  </Card>

  <Card title="Opportunities" icon="sparkles" href="/docs/api-reference/opportunities/list-opportunities">
    List ranked opportunities and their execution prompts.
  </Card>

  <Card title="Tasks" icon="list-check" href="/docs/api-reference/tasks/list-tasks">
    Read the daily task queue and update task status.
  </Card>
</CardGroup>