Jupyter Notebook Refactoring

VerifiedSafe

Analyzes Jupyter Notebook (.ipynb) files as JSON to identify and batch replace specific import statements or code blocks. Helps when renaming modules, updating function calls, or standardizing code patterns across multiple notebooks in a directory.

Sby Skills Guide Bot
DevelopmentIntermediate
1506/2/2026
Claude CodeCursorWindsurfCodex
#jupyter#notebook#refactoring#batch-replace#code-analysis

Recommended for

Our review

Programmatically analyzes and performs batch replacement of import patterns or code blocks within Jupyter Notebook (.ipynb) files.

Strengths

  • Enables precise regex-based search and replacement across multiple notebooks
  • Preserves notebook JSON structure and cell source format
  • Automates repetitive refactoring tasks that would be error-prone manually

Limitations

  • Requires careful regex to avoid unintended changes
  • Not suitable for semantic transformations (e.g., renaming variables beyond simple strings)
  • May need manual review after batch replacement to ensure correctness
When to use it

Use this skill when you need to update import statements, deprecated functions, or code patterns across a large number of Jupyter notebooks.

When not to use it

Avoid this skill for one-off edits in a single notebook or when the transformation requires understanding of runtime state or data dependencies.

Security analysis

Safe
Quality score85/100

The skill performs local file manipulations on Jupyter notebooks using Python and does not execute arbitrary shell commands, exfiltrate data, or disable security features. It uses standard JSON parsing and writing, with no destructive patterns.

No concerns found

Examples

Replace import statement in all notebooks
Replace all occurrences of 'from gwexpy.noise import asd' with 'from gwexpy.noise import asd_updated' in every .ipynb file under the current directory.
Rename function call across multiple notebooks
In all Jupyter notebooks in the 'experiments' folder, replace 'old_function(' with 'new_function(' in all code cells.
Change plotting library import
Replace 'import matplotlib.pyplot as plt' with 'import seaborn as sns' in all code cells of notebooks in the 'reports' subdirectory.

name: refactor_nb description: Jupyter Notebook (.ipynb) 内のコード要素を一括置換・リファクタリングする

refactor_notebooks Skill

This skill is for programmatically analyzing Jupyter Notebook (.ipynb) files and performing batch replacement or modification of specific import patterns or code blocks.

Instructions

  1. Analyze Notebook Structure:

    • Load .ipynb files as JSON using Python and iterate through the cells list.
    • Verify if the cell_type of each cell is code.
  2. Filter and Match:

    • Join the source field (list format) into a string and use regular expressions or keyword matching to identify target cells.
    • Target specific import statements (e.g., from gwexpy.noise import asd), function calls, or targeted comments.
  3. Implement Transformation:

    • Create a transformation script to rewrite the source list of the cells in memory.
    • The updated source must be in list format (each element as a string ending with a newline).
  4. Write and Verify:

    • Save the file using json.dump, maintaining an indent of 1 (a gwexpy convention) and specifying ensure_ascii=False.
    • Verify that the resulting notebook is valid JSON and that the intended changes have been applied using view_file or similar.

Usage Guidelines

  • When modifying multiple notebooks across a directory, create a loop script that collects .ipynb files using glob or similar.
  • For complex refactoring, adopt a workflow of saving the logic as a temporary .py script, executing it via run_command, and then deleting the script.
Related skills