Credentials. Scheduled runs need access to your Git host and model provider, so make sure the credentials used are scoped to read-only access where possible.
Who it is forA team lead or maintainer who wants a regular status report on open pull requests and review progress.
The problemChecking open PRs by hand every morning is repetitive and easy to forget.
The outcomeCline runs the same prompt on a schedule and produces a PR status summary each weekday morning.
What you need first
- Node.js with npm available, since the README installs the CLI with npm
- Access to an AI model provider that Cline supports, such as Anthropic, OpenAI, Google, OpenRouter, or a local model through Ollama or LM Studio
- A git repository or project folder you want the agent to work in
- For the VS Code path: the VS Code editor and the VS Code Marketplace extension
Steps
- Install the CLI with
npm i -g cline. - Confirm the repository path you want the agent to read.
- Run
cline schedule create "PR summary" --cron "0 9 * * MON-FRI" --prompt "List all open PRs and their review status" --workspace /path/to/repo, replacing the workspace path with your own. (inferred, check the README) - Check that the schedule persists after you close the terminal and restart the machine.
- Review the first scheduled output and adjust the prompt if it misses information you need.
Prompt for your agent
Use the cline/cline CLI to create a schedule in <repo-path> that runs every weekday at 9 AM and lists open pull requests with their review status. Run the `cline schedule create` command from the README with that workspace, then verify the schedule exists and report its next run time.
Caveat. The README says schedules run independently of a terminal, but it does not say how the PR data is fetched, so confirm the output matches what you see on your Git host.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page