Convert commands and context to skills, add skills symlinks to Rexfile

Move purge-file-from-git, compose-blog-post, increment-version-and-push
from commands to skills format, and convert go-best-practices from context
to a skill. Update Rexfile home_prompts task to symlink both commands and
skills directories for cursor, claude, agents, and opencode.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

3 files changed, 0 insertions, 74 deletions

diff --git a/prompts/commands/compose-blog-post.md b/prompts/commands/compose-blog-post.md
deleted file mode 100644
index 7af3d55..0000000
--- a/prompts/commands/compose-blog-post.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Compose blog post
-
-Compose a blog post in ~/git/foo.zone-content/gemtext/gemfeed/ in gemtext format.
-
-1. Read 2-3 recent blog posts from the gemfeed directory to match the existing style (title, published date, TOC, links, closing).
-2. Use the filename format: `YYYY-MM-DD-slug.gmi.tpl` (ask for the date and slug if not specified).
-3. Follow the gemtext conventions from existing posts:
-   - `# Title` as first line
-   - `> Published at` with ISO 8601 timestamp and timezone
-   - `<< template::inline::toc` after the intro paragraph
-   - `=> ./slug/image.ext Description` for images (create an asset directory named after the slug if images are needed)
-   - `=> URL Description` for external links
-   - Section headers with `##` and `###`
-   - Code blocks with triple backticks
-   - Closing with `E-Mail your comments to paul@nospam.buetow.org :-)` and related posts index
-   - `=> ../ Back to the main site` as the last line
-4. Ask what the blog post should be about if no topic is given.
-5. Show a preview before writing the file.
diff --git a/prompts/commands/increment-version-and-push.md b/prompts/commands/increment-version-and-push.md
deleted file mode 100644
index 015038b..0000000
--- a/prompts/commands/increment-version-and-push.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# Increment version and push
-
-Increment the version of the project, tag it in git, commit, and push. For Go-based projects, look for the internal/version.go file. For bug fixes, increment only the minor version. We are using semantic versioning, e.g., x.y.z, where z is the minor version. For new features, increment y. Never increment x (the major version) unless specified.
diff --git a/prompts/commands/purge-file-from-git.md b/prompts/commands/purge-file-from-git.md
deleted file mode 100644
index 67736cc..0000000
--- a/prompts/commands/purge-file-from-git.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# /purge-file-from-git
-
-**Description:** Completely remove a file from git history using git-filter-repo. This is a destructive operation that rewrites history and requires force-pushing.
-
-**Parameters:**
-- file_path: The relative path to the file to purge from git history (e.g., "secrets.env", "large-file.bin", "./config/passwords.txt")
-
-**Example usage:**
-- `/purge-file-from-git secrets.env`
-- `/purge-file-from-git config/api-keys.json`
-- `/purge-file-from-git data/large-dataset.csv`
-
----
-
-## Prompt
-
-I'll purge `{{file_path}}` from the entire git history. This is a **destructive operation** that will:
-
-1. **Rewrite all commits** in the repository's history
-2. **Change commit hashes** for affected commits and their descendants
-3. **Require a force-push** if already pushed to remote
-4. **Potentially cause issues** for collaborators who have cloned the repo
-
-**Before proceeding, I need to confirm:**
-
-1. **Is this branch shared with others?** If so, they'll need to re-clone or carefully rebase after this operation.
-2. **Have you pushed this branch to a remote?** If yes, you'll need to force-push afterward.
-3. **Do you want to proceed with rewriting the git history?**
-
-Once confirmed, I will:
-
-### Process:
-
-1. **Verify prerequisites**:
-   - Check if `git-filter-repo` is installed (install if needed)
-   - Check current git status
-
-2. **Execute purge**:
-   - Clean any previous filter-repo state
-   - Use `git filter-repo --path {{file_path}} --invert-paths --force`
-   - Restore the origin remote (filter-repo removes it as a safety measure)
-
-3. **Ask about .gitignore**:
-   - Prompt: "Would you like to add `{{file_path}}` to .gitignore to prevent future accidental commits?"
-   - If yes: Add the file to .gitignore and commit the change
-   - If no: Skip this step
-
-4. **Provide next steps**:
-   - Explain how to force-push: `git push --force origin <branch>`
-   - Warn about impact on collaborators
-   - Provide recovery instructions for team members
-
-Let me know if you want to proceed with purging `{{file_path}}` from git history.