DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to plan a feature in VS Code and approve each edit with Cline

Use Plan mode to map out a change, then Act mode to apply it with per-edit approval.

Who it is forA developer working in VS Code who wants an AI assistant to make a multi-file change without losing control of what gets written.

The problemLetting an agent edit many files at once is risky when each change is hard to inspect.

The outcomeThe developer approves a plan, then reviews each file diff and can revert any change with checkpoints.

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

  1. Install Cline from the VS Marketplace inside VS Code.
  2. Open your project folder in VS Code.
  3. Switch Cline to Plan mode and describe the feature so it can explore the codebase and propose a strategy.
  4. Switch to Act mode once the plan looks right, and approve each file edit and terminal command as it appears.
  5. Review each diff, and use the checkpoints to undo any change you do not want.

Prompt for your agent

Work in the cline/cline VS Code extension on the project at <project-path>. Ask Cline in Plan mode to outline how to add <feature-description>, then switch to Act mode and apply it. Report the files changed and confirm that each change appears as a reviewable diff.

Caveat. The README says auto-approve is available, but approving each edit manually is the safer default for a first run on a real project.

Share: 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