mitsupi 1.0.0

package/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+	http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/README.md

@@ -0,0 +1,95 @@
+# Agent Stuff
+
+This repository contains command files and skills that I use in some form with projects.  Note that I usually fine-tune these for projects so they might not work without modification for you.
+
+## Commands
+
+All command files are in the [`commands`](commands) folder:
+
+* [`/handoff`](commands/handoff.md) - Creates detailed handoff plan for session continuation
+* [`/pickup`](commands/pickup.md) - Resumes work from previous handoff session
+* [`/make-release`](commands/make-release.md) - Automates repository release with version management
+* [`/update-changelog`](commands/update-changelog.md) - Updates changelog with recent commits
+
+### Handoff/Pickup Usage
+
+These are inspired by the idea of Ampcode to replace `/compact` with handoff.  I generally do this already by hand with copy/paste but this is an attempt of automating this:
+
+```
+/handoff "implement phase 1 of our plan"
+```
+
+It will write a handoff plan into .claude/handoffs which you can then continue in a new session:
+
+```
+/pickup name-of-handoff
+```
+
+### Release Management
+
+The release management commands do not work without tuning!  But you can put claude to them and derive actually working ones.  I for instance use them in [absurd](https://github.com/earendil-works/absurd) and you can look at the repo to see them in use.
+
+## Skills
+
+All skill files are in the [`skills`](skills) folder:
+
+* [`/ghidra`](skills/ghidra) - Claude Skill for reverse engineering binaries using Ghidra's headless analyzer
+* [`/web-browser`](skills/web-browser) - Claude Skill for using Puppeteer in a Node environment to browse the web
+* [`/tmux`](skills/tmux) - Claude Skill for driving tmux directly with keystrokes and pane output scraping
+* [`/sentry`](skills/sentry) - Alternative way to access Sentry as a Claude Skill for reading issues
+* [`/improve-skill`](skills/improve-skill) - Claude Skill for analyzing coding agent sessions to improve or create new skills
+* [`/pi-share`](skills/pi-share) - Claude Skill for loading and parsing session transcripts from shittycodingagent.ai
+* [`/anachb`](skills/anachb) - Claude Skill for querying Austrian public transport (VOR AnachB) for departures, routes, and disruptions
+* [`/oebb-scotty`](skills/oebb-scotty) - Claude Skill for Austrian rail travel planning via ÖBB Scotty API
+
+### Browser
+
+In the [`skills/web-browser`](skills/web-browser) folder is a Claude Skill that helps it to use puppeteer in a node environment to browse the web.  This significantly improves on using a browser MCP.  You will need to go into the scripts folder once to run `npm i`.  This was stolen from [Mario Zechner](https://mariozechner.at/posts/2025-11-02-what-if-you-dont-need-mcp/).
+
+### tmux
+
+In the [`skills/tmux`](skills/tmux) folder is a Claude Skill that lets it drive tmux directly for interactive CLI workflows (python, gdb, etc.) by sending keystrokes and scraping pane output.  It uses stock tmux on macOS/Linux and includes helper scripts in `scripts` to find sessions and wait for prompts.
+
+### sentry
+
+In the [`skills/sentry`](skills/sentry) folder there is an alternative way to access Sentry as a Claude Skill.  I found the other methods to talk to Sentry token inefficient and just not great.  Right now it can only read issues though and might not be ideal yet.
+
+### improve-skill
+
+In the [`skills/improve-skill`](skills/improve-skill) folder is a skill that helps analyze coding agent sessions to improve or create new skills.  It works with Claude Code, Pi, and Codex session files.  Ask the agent to "improve the sentry skill based on this session" or "create a new skill from this session" to use it.
+
+### ghidra
+
+In the [`skills/ghidra`](skills/ghidra) folder is a skill for automated reverse engineering using Ghidra's headless analyzer.  It can decompile binaries to C code, extract functions, strings, symbols, and analyze call graphs without needing the GUI.  Requires Ghidra installed (on macOS: `brew install --cask ghidra`).
+
+### pi-share
+
+In the [`skills/pi-share`](skills/pi-share) folder is a skill for loading and parsing session transcripts from shittycodingagent.ai (pi-share) URLs.  It fetches gists, decodes embedded session data, and extracts conversation history including messages, tool calls, and system prompts.
+
+### google-meet
+
+In the [`skills/google-meet`](skills/google-meet) folder is a skill for creating Google Meet spaces with auto recording/transcription enabled.  It is currently hardcoded for earendil.com accounts only.
+
+### anachb
+
+In the [`skills/anachb`](skills/anachb) folder is a skill for querying Austrian public transport via the VOR AnachB API.  It includes shell scripts for searching stations, getting real-time departures, planning routes between locations, and checking service disruptions.  Covers all Austrian public transport including trains, U-Bahn, trams, and buses.
+
+### oebb-scotty
+
+In the [`skills/oebb-scotty`](skills/oebb-scotty) folder is a skill for Austrian rail travel planning via the ÖBB Scotty HAFAS API.  It documents how to search locations, plan trips between stations, get departure/arrival boards, and fetch service alerts.  Includes jq filters for extracting concise trip summaries from verbose API responses.
+
+## PI Coding Agent Extensions
+
+Custom extensions for the PI Coding Agent can be found in the [`pi-extensions`](pi-extensions) folder:
+
+* [`qna.ts`](pi-extensions/qna.ts) - Extracts questions from the last assistant message into the editor for easy answering. Uses Claude Haiku for cost-efficient extraction when available.
+* [`answer.ts`](pi-extensions/answer.ts) - Alternative to `qna.ts` with a custom interactive TUI for answering questions one by one.
+* [`review.ts`](pi-extensions/review.ts) - Code review command inspired by Codex. Supports reviewing uncommitted changes, against a base branch (PR style), specific commits, or with custom instructions. Includes Ctrl+R shortcut.
+* [`loop.ts`](pi-extensions/loop.ts) - Runs a prompt loop for rapid iterative coding with optional auto-continue control.
+* [`reveal.ts`](pi-extensions/reveal.ts) - Finder/Quick Look helper that browses session file references via Ctrl+F or `/files`, with Ctrl+R revealing the latest file and Ctrl+Shift+R opening Quick Look on macOS.
+* [`cwd-history.ts`](pi-extensions/cwd-history.ts) - Displays and manages recent working directory history inside the PI Coding Agent.
+* [`codex-tuning.ts`](pi-extensions/codex-tuning.ts) - Codex tuning helper for collecting samples and tagging outcomes during agent sessions.
+
+## PI Coding Agent Themes
+
+This repository includes custom themes for the PI Coding Agent. The themes can be found in the [`pi-themes`](pi-themes) folder and customize the appearance and behavior of the agent interface.

package/TODO.md

@@ -0,0 +1,11 @@
+- [ ] We need a way for the div viewer to select small hunks because when the review div tool actually comes by and is used for large changes it just throws way too much stuff into the UI. 
+
+
+1. Global state is module-scoped — If the extension is loaded once but used across multiple concurrent sessions (hypothetically),
+ they'd share state. Is that a concern in pi's architecture?
+ 2. session_switch skips UI restoration (restoreUI = false) — Why? If I switch to a session that was mid-review, I'd expect the widget
+ to reappear.
+ 3. Comments aren't cleared when entering a new review — executeReview() sets reviewActive = true but doesn't reset comments = []. If a
+ previous review left stale comments and reconstructState didn't run (e.g., same session), they'd accumulate.
+ 4. No explicit persistence of comments — They survive only because tool results are in the session log. But if the session is truncated
+ or the tool result is pruned, comments could be lost silently.

package/commands/handoff.md

@@ -0,0 +1,100 @@
+Creates a detailed handoff plan of the conversation for continuing the work in a new session.
+
+The user specified purpose:
+
+<purpose>$ARGUMENTS</purpose>
+
+You are creating a summary specifically so that it can be continued by another agent.  For this to work you MUST have a purpose.  If no specified purpose was provided in the `<purpose>...</purpose>` tag you must STOP IMMEDIATELY and ask the user what the purpose is.
+
+Do not continue before asking for the purpose as you will otherwise not understand the instructions and do not assume a purpose!
+
+## Goal
+
+Your task is to create a detailed summary of the conversation so far, paying close attention to the user's explicit purpose for the next steps.
+This handoff plan should be thorough in capturing technical details, code patterns, and architectural decisions that will be essential for continuing development work without losing context.
+
+## Process
+
+Before providing your final plan, wrap your analysis in <analysis> tags to organize your thoughts and ensure you've covered all necessary points. In your analysis process:
+
+1. Chronologically analyze each message and section of the conversation. For each section thoroughly identify:
+   - The user's explicit requests and intents
+   - Your approach to addressing the user's requests
+   - Key decisions, technical concepts and code patterns
+   - Specific details like file names, full code snippets, function signatures, file edits, etc
+2. Double-check for technical accuracy and completeness, addressing each required element thoroughly.
+
+Your plan should include the following sections:
+
+1. **Primary Request and Intent**: Capture all of the user's explicit requests and intents in detail
+2. **Key Technical Concepts**: List all important technical concepts, technologies, and frameworks discussed.
+3. **Files and Code Sections**: Enumerate specific files and code sections examined, modified, or created. Pay special attention to the most recent messages and include full code snippets where applicable and include a summary of why this file read or edit is important.
+4. **Problem Solving**: Document problems solved and any ongoing troubleshooting efforts.
+5. **Pending Tasks**: Outline any pending tasks that you have explicitly been asked to work on.
+6. **Current Work**: Describe in detail precisely what was being worked on immediately before this handoff request, paying special attention to the most recent messages from both user and assistant. Include file names and code snippets where applicable.
+7. **Optional Next Step**: List the next step that you will take that is related to the most recent work you were doing. IMPORTANT: ensure that this step is DIRECTLY in line with the user's explicit requests, and the task you were working on immediately before this handoff request. If your last task was concluded, then only list next steps if they are explicitly in line with the users request. Do not start on tangential requests without confirming with the user first.
+
+Additionally create a "slug" for this handoff.  The "slug" is how we will refer to it later in a few places.  Examples:
+
+* current-user-api-handler
+* implement-auth
+* fix-issue-42
+
+Together with the slug create a "Readable Summary".  Examples:
+
+* Implement Current User API Handler
+* Implement Authentication
+* Fix Issue #42
+
+## Output Structure
+
+Here's an example of how your output should be structured:
+
+```markdown
+# Readable Summary
+
+<analysis>
+[Your thought process, ensuring all points are covered thoroughly and accurately]
+</analysis>
+
+<plan>
+# Session Handoff Plan
+
+## 1. Primary Request and Intent
+[Detailed description of all user requests and intents]
+
+## 2. Key Technical Concepts
+- [Concept 1]
+- [Concept 2]
+- [...]
+
+## 3. Files and Code Sections
+### [File Name 1]
+- **Why important**: [Summary of why this file is important]
+- **Changes made**: [Summary of the changes made to this file, if any]
+- **Code snippet**:
+```language
+[Important Code Snippet]
+```
+
+### [File Name 2]
+- **Code snippet**:
+```language
+[Important Code Snippet]
+```
+
+[...]
+
+## 4. Problem Solving
+[Description of solved problems and ongoing troubleshooting]
+
+## 5. Next Step
+[Required next step to take, directly aligned with user's explicit handoff purpose]
+</plan>
+```
+
+## Final Step
+
+After providing your analysis and summary, write the handoff summary to a markdown file at `.claude/handoffs/[timestamp]-[slug].md` where [timestamp] is the current date in format YYYY-MM-DD and the slug is what we defined before.
+
+Then tell the user about this file and that they can use `/pickup FILENAME` to continue.

package/commands/make-release.md

@@ -0,0 +1,75 @@
+Make a release of this repository.
+
+Version or release type: "$ARGUMENTS"
+
+## Step-by-Step Process:
+
+### 1. Determine the target version
+
+The `$ARGUMENTS` can be either:
+- An explicit version number (e.g., `0.0.4`) - recommended for making a specific release
+- A release type: `patch`, `minor`, or `major` - which will bump from the current version
+
+If `$ARGUMENTS` is an explicit version (e.g., `0.0.4`):
+- Use that version directly as `$NEW_VERSION`
+- This is the recommended approach as it allows retrying failed releases
+
+If `$ARGUMENTS` is a release type (`patch`, `minor`, or `major`):
+- Determine what the new version will be by running:
+  ```bash
+  cd sdks/typescript
+  CURRENT_VERSION=$(node -p "require('./package.json').version")
+  NEW_VERSION=$(npm version $ARGUMENTS --no-git-tag-version | sed 's/^v//')
+  git checkout package.json package-lock.json  # Revert the changes
+  cd ../..
+  echo "Will release version: $NEW_VERSION"
+  ```
+- Then use this `$NEW_VERSION` for the rest of the process
+
+If no argument is provided, ask the user which version or type to use.
+
+### 2. Update the changelog
+
+Run the `/update-changelog` command to ensure the changelog is up to date with recent changes.
+
+### 3. Verify the version number
+
+Double-check that `$NEW_VERSION` is correct before proceeding.
+
+### 4. Update CHANGELOG.md
+
+Edit the `CHANGELOG.md` file:
+- Change the `# Unreleased` heading to `# $NEW_VERSION`
+- Add a new `# Unreleased` section at the top (empty for now)
+
+### 5. Run the release script
+
+Execute the release script with the explicit version number (NOT the release type):
+
+```bash
+./scripts/release.sh $NEW_VERSION
+```
+
+**Important:** Always pass the explicit version number (e.g., `0.0.4`) to the release script, not the release type (e.g., `patch`). This ensures that aborted releases can be retried without incrementing the version.
+
+This script will:
+- Update the version in `sdks/typescript/package.json` (or skip if already set)
+- Update `package-lock.json`
+- Create a commit with message "Release $NEW_VERSION"
+- Create a git tag with the version number
+
+### 6. Show push instructions
+
+After the release script completes, show the user the commands to push:
+
+```bash
+git push origin main && git push origin $NEW_VERSION
+```
+
+**Important:** Do NOT automatically push. Let the user review the commit and tag first, then they can manually run the push commands.
+
+## Notes
+
+- The release script will check for a clean working directory
+- It will verify that CHANGELOG.md has a section for the new version
+- The user should review the commit and tag before pushing

package/commands/pickup.md

@@ -0,0 +1,30 @@
+Resumes work from a previous handoff session which are stored in `.claude/handoffs`.
+
+The handoff folder might not exist if there are none.
+
+Requested handoff file: `$ARGUMENTS`
+
+## Process
+
+### 1. Check handoff file
+
+If no handoff file was provided, list them all.  Eg:
+
+
+```
+echo "## Available Handoffs"
+echo ""
+for file in .claude/handoffs/*.md; do
+  if [ -f "$file" ]; then
+    title=$(grep -m 1 "^# " "$file" | sed 's/^# //')
+    basename=$(basename "$file")
+    echo "* \`$basename\`: $title"
+  fi
+done
+echo ""
+echo "To pickup a handoff, use: /pickup <filename>"
+```
+
+### 2. List handoff file
+
+If a handoff file was provided locate it in `.claude/handoffs` and read it.  Note that this file might be misspelled or the user might have only partially listed it.  If there are multiple matches, ask the user which one they want to continue with.  The file contains the instructions for how you should continue.

package/commands/update-changelog.md

@@ -0,0 +1,78 @@
+Please update the `CHANGELOG.md` for thie repository with changes between the last release and the current version (`main`) which were not incorporated yet.
+
+Base line version: "$ARGUMENTS"
+
+## Step-by-Step Process:
+
+### 1. Determine baseline version
+If no baseline version is provided, use the most recent git tag. You can find it with `git describe --tags --abbrev=0`.
+
+### 2. Find the commits from git
+
+Use the following commands to gather commit information:
+
+```bash
+# Get the baseline version (if not provided)
+git describe --tags --abbrev=0
+
+# Get all commits since the baseline version
+git log <baseline-version>..HEAD
+```
+
+### 3. Update the changelog
+Read the already existing `CHANGELOG.md` and check if there are changes not yet incorporated, then add them. Always add them to the "Unreleased" section only. If there is none yet, add it on the top.
+
+## Ground Rules When Writing Changelogs
+
+### Content Guidelines
+* Focus on **notable changes** that affect users (features, fixes, breaking changes)
+* Mention pull requests (`#NUMBER`) when available, but not raw commit hashes
+* Ignore insignificant changes (typo fixes, internal refactoring, minor documentation updates)
+* Group related changes together when appropriate
+* Order entries by importance: breaking changes first, then features, then fixes
+
+### Style Guidelines
+* Use valid markdown syntax
+* Start each entry with a past-tense verb or descriptive phrase
+* Keep entries concise but descriptive enough to understand the change
+* Use bullet points (`*` or `-`) for individual changes
+* Format code references with backticks (e.g., `` `foo.cleanup` ``)
+
+### Example Format
+
+Here's an example of well-formatted changelog entries (from minijinja):
+
+```markdown
+## 2.13.0
+
+* Added multi-key support to the `|sort` filter.  #827
+* Fix `not undefined` with strict undefined behavior.  #838
+* Added support for free threading Python.  #841
+
+## 2.12.0
+
+* Item or attribute lookup will no longer swallow all errors in Python.  #814
+* Added `|zip` filter.  #818
+* Fix `break_on_hyphens` for the `|wordwrap` filter.  #823
+* Prefer error message from `unknown_method_callback`.  #824
+* Ignore `.jinja` and `.jinja2` as extensions in auto escape.  #832
+```
+
+### Good vs. Bad Examples
+
+**Good:**
+* `Fixed an issue with the TypeScript SDK which caused an incorrect config for CJS.`
+* `Added support for claim timeout extension on checkpoint writes.`
+* `Improved error reporting when task claim expires.`
+
+**Bad:**
+* `Fixed bug` (too vague)
+* `Updated dependencies` (insignificant unless it fixes a security issue)
+* `Refactored internal code structure` (internal change, not user-facing)
+* `Fixed typo in comment` (insignificant)
+
+## Notes
+
+* If the current CHANGELOG.md already has an "Unreleased" section with content, append to it rather than replacing it
+* Preserve the existing changelog style and formatting
+* When in doubt about whether a change is significant, err on the side of including it

package/package.json

@@ -0,0 +1,22 @@
+{
+  "name": "mitsupi",
+  "version": "1.0.0",
+  "description": "Pi extensions, skills, and themes",
+  "type": "module",
+  "keywords": [
+    "pi-package",
+    "pi-extension",
+    "pi-skill",
+    "pi-theme"
+  ],
+  "pi": {
+    "extensions": ["./pi-extensions/*.ts"],
+    "skills": ["./skills"],
+    "themes": ["./pi-themes/*.json"]
+  },
+  "peerDependencies": {
+    "@mariozechner/pi-coding-agent": "*",
+    "@mariozechner/pi-ai": "*",
+    "@mariozechner/pi-tui": "*"
+  }
+}