Nano Banana Pro

What Is This?

Overview

Nano Banana Pro is an intelligent file editing assistant that reads, modifies, and creates text files with precision and safety. The skill operates through a read-first workflow that examines files before making changes, ensuring edits are accurate and intentional. It supports exact string replacements, multi-line edits, and batch operations across multiple files.

At its core, Nano Banana Pro provides three primary editing modes: reading files to understand their content, editing existing files with precise string replacements, and writing new files when needed.

Who Should Use This

Developers: Perfect for precise code changes, refactoring variable names, or updating configuration files.

Technical Writers: Ideal for editing documentation and making consistent terminology changes.

DevOps Engineers: Excellent for updating configuration files and batch processing server configurations.

System Administrators: Great for managing system configuration files and maintaining consistent settings.

Why Use It?

Problems It Solves

Risky Manual Edits: Manual editing can lead to typos or missed instances. Nano Banana Pro makes exact replacements with verification, ensuring changes are applied correctly.

Lack of Context: Editing without understanding full file content risks breaking dependencies. The skill always reads files first before making modifications.

Batch Editing Complexity: Changing the same text across multiple files manually is error-prone. The skill processes multiple files systematically while maintaining accuracy.

Format Preservation: Maintaining proper indentation and code structure during edits is challenging. The skill preserves formatting automatically while making targeted changes.

Core Highlights

• Precision String Matching: Performs exact replacements with case-sensitive matching.
• Read Before Edit: Always examines files before modification to prevent errors.
• Multi-line Support: Handles replacements spanning multiple lines.
• Batch Operations: Processes multiple files with consistent changes.
• Replace All Mode: Updates every occurrence of a string in one operation.
• Edit Verification: Confirms changes were applied correctly after each operation.

How to Use It?

Basic Usage

The fundamental workflow starts with reading a file to understand its contents, then making precise edits using exact string matching. To change a function name, read the file first, identify the exact text to replace including surrounding context, then execute the replacement.

1. Read the target file
2. Identify exact text to replace (including indentation and context)
3. Specify the new text
4. Apply the edit and verify

Specific Scenarios

Variable Renaming

Replace "oldVariableName" with "newVariableName" using replace_all mode.

Configuration Updates

Read config file, locate exact setting line, replace with updated value.

Multi-line Refactoring

Identify function block with proper indentation,
replace entire block with refactored version.

Real-World Examples

API Endpoint Update: When migrating APIs, read all relevant files to find endpoint references, then systematically replace the old base URL with the new one across multiple service files.

Configuration Migration: When updating from JSON to YAML format, read the existing config, transform the structure, then write the new file while maintaining all settings.

Advanced Tips

For complex refactoring, include enough surrounding context in replacement strings to make them unique. If "function test()" appears multiple times, include the preceding comment or following code to uniquely identify each instance. Use replace_all when renaming identifiers throughout a file, but read first to verify no false positives exist.

When to Use It?

Use Cases

Code Refactoring: Rename variables, functions, or classes consistently across files while maintaining structure.

Configuration Management: Update settings files or deployment scripts with precise value changes.

Documentation Updates: Make terminology changes or correct information across multiple files.

Format Standardization: Fix indentation issues or standardize code style across a project.

Dependency Updates: Change import statements or update package references in configuration files.

Important Notes

Requirements

Must use absolute file paths rather than relative paths. Files must be text-based and readable in standard encodings. For edit operations, the old string must exist exactly as specified in the target file.

Usage Recommendations

Do:

• Read files before attempting edits to understand context and structure.
• Include context in replacement strings to ensure uniqueness.
• Verify changes after edits by reading the modified sections.
• Use absolute paths to avoid ambiguity.
• Test on copies first when making complex or risky changes.

Don't:

• Skip reading files before editing, as this leads to failed operations.
• Use vague strings that might match multiple unintended locations.
• Forget indentation when specifying replacement text, as exact matching includes whitespace.
• Edit without backup when working with critical files lacking version control.

Limitations

Exact Matching Required: Replacements require exact string matches including all whitespace. Small differences will cause operations to fail.

No Pattern Matching: The skill uses literal string replacement rather than regular expressions.

Single File Focus: Each operation targets one file at a time, requiring multiple sequential operations for batch processing.