update-analysis-injection-notebook

Update analysis injection notebooks and hook configurations for new package versions.

1|Updated Sep 30, 2023
One-click install
npx skills add https://github.com/speediedan/interpretune --skill update-analysis-injection-notebook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-analysis-injection-notebook
Source: https://github.com/speediedan/interpretune/tree/main/.github/skills/update-analysis-injection-notebook
Command: npx skills add https://github.com/speediedan/interpretune --skill update-analysis-injection-notebook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of updating analysis injection notebooks and their configurations when an upstream package changes versions, ensuring compatibility and accuracy.

Core Features & Use Cases

  • Automated Version Sync: Updates notebook configurations and documentation to match new package versions.
  • Regex Validation & Fixes: Identifies and corrects broken regex patterns used for code analysis hooks.
  • End-to-End Validation: Runs tests to confirm that all updates are functional and non-breaking.
  • Use Case: When the circuit-tracer library is updated from v0.1.0 to v0.4.0, this Skill can be used to automatically adjust the analysis injection hooks in the attribution_analysis notebook to work with the new code, update its documentation, and verify everything passes tests.

Quick Start

Use the update-analysis-injection-notebook skill to update the attribution_analysis notebook for circuit-tracer version 0.4.0.

Frequently Asked Questions about update-analysis-injection-notebook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix analysis injection notebooks when a package update breaks compatibility?

To fix analysis injection notebooks after a package update breaks compatibility, you need to update hook configurations, validate regex patterns, and run end-to-end tests to ensure everything works. This Skill automates that entire version sync process.

What is the best way to update regex patterns for code analysis hooks after an upstream version change?

The best way to update regex patterns for code analysis hooks after an upstream version change is to validate and correct the broken patterns against the new package version, then update the documentation and run tests to confirm non-breaking updates.

How does notebook analysis injection hook synchronization work with configuration management?

Notebook analysis injection hook synchronization works by updating configurations and documentation to match new package versions, addressing compatibility issues arising from upstream code modifications to ensure the hooks remain functional and accurate.

Can I automatically validate end-to-end tests for analysis notebooks following a library version bump?

Yes, you can automatically validate end-to-end tests for analysis notebooks following a library version bump. This Skill runs tests to confirm that all configuration updates and regex fixes are functional and non-breaking after the package changes.

Do I need to manually adjust documentation when updating analysis injection notebooks for target package versions?

No, you do not need to manually adjust documentation when updating analysis injection notebooks for target package versions. This Skill updates the documentation automatically to match the new package versions during the synchronization process.

Why does my analysis injection notebook fail after an upstream code modification?

Your analysis injection notebook fails after an upstream code modification because compatibility issues arise from the package changes, breaking existing regex patterns and hook configurations that require validation and updates to function correctly.