organise-tool

Migrate Pixie tool Python files into a src/ package with tests and CHANGELOG.

6|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/AlexKapadia/Pixie --skill organise-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organise-tool
Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/organise-tool
Command: npx skills add https://github.com/AlexKapadia/Pixie --skill organise-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restructures one Pixie tool's internal Python files into the src/ layout, adding tests/, notebooks/, CHANGELOG skeletons, then re-validates. Use when the user asks to organise, tidy, refactor, restructure, or clean up a tool's files or layout. Do NOT use to change inputs (update-tool), rename (rename-tool), or fix broken (debug-tool).

Core Features & Use Cases

  • Move loose .py files into src/<package>/, create tests/ and notebooks/ if missing, and generate a CHANGELOG.md skeleton to document changes.
  • Update imports in main.py to reflect the new package path and adjust pyproject.toml for src-layout builds.
  • Validate the tool layout end-to-end and re-run Pixie’s internal checks to ensure the tool remains functional.

Quick Start

Ask for the target tool and confirm a move plan before executing.

Frequently Asked Questions about organise-tool

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

FAQPage Schema
How do I restructure a Pixie tool's Python files into a src layout?

Restructuring a Pixie tool into a src layout migrates loose Python files into a src/ package, adds tests/ and notebooks/ directories, and generates a CHANGELOG skeleton to standardize the codebase for improved maintainability.

What happens to imports and pyproject.toml when migrating to a src layout?

Migrating to a src layout updates imports in main.py to reflect the new package path and adjusts pyproject.toml build configurations to support the src-layout structure.

How do I add tests and a CHANGELOG to an existing Pixie tool codebase?

Adding tests and a CHANGELOG to an existing Pixie tool creates tests/ and notebooks/ directories if missing, generates a CHANGELOG.md skeleton, and re-validates the tool end-to-end to ensure functionality is preserved.

Does the src layout reorganization fix broken tools or change tool inputs?

Src layout reorganization does not fix broken tools or change inputs. It organizes loose Python files and should not be used for debugging, updating inputs, or renaming tools.

How do I validate a Pixie tool after reorganizing its file layout?

Validating a Pixie tool after reorganizing its file layout runs end-to-end checks and Pixie's internal validations to ensure the tool remains fully functional after imports and build configs are updated.