gitea-wiki_skill

Overview

This skill manages Gitea wiki pages by providing clear workflows and shell-first patterns for reading, creating, updating, and deleting wiki content. It focuses on safe handling of base64-encoded page content and uses temporary files and standard Bash utilities to encode/decode content before calling the repository API. The goal is reliable wiki edits while avoiding inline large base64 strings.

How this skill works

The skill uses the Gitea wiki API wrappers to list pages, fetch page content (as base64), create new pages, update existing pages, delete pages, and retrieve revision history. For reading and editing, content is decoded to a temporary file using base64 -d, edited locally, then re-encoded with base64 and sent back to the API. It enforces using tr -d '\n' when encoding so the API receives single-line base64 payloads and recommends cleaning up temporary files after operations.

When to use it

• You need to read or audit existing Gitea wiki pages and their revision history.
• You want to create new documentation pages in a Gitea wiki from local files or editor edits.
• You must update an existing wiki page with tracked commits and messages.
• You need to remove obsolete wiki pages safely and confirm deletions.
• You want reproducible shell-based workflows for wiki content encoding/decoding.

Best practices

• Always decode content to a temp file (for example /tmp/wiki-*.md) before reading or editing.
• When encoding, use: base64 < /tmp/file.md | tr -d '\n' to produce a single-line payload.
• Include a clear commit message on create/update operations to document intent.
• Remove temporary files after operations to avoid leaking content or cluttering the environment.
• Fetch and inspect revision history before making breaking changes to important pages.

Example use cases

• Fetch the Home page, decode it to /tmp/wiki-home.md, review and then re-encode to propose edits.
• Create an Installation page by writing a local markdown file, encoding it, and calling the create endpoint.
• Update API docs: pull current content, make edits in your editor, re-encode and update the wiki with a commit message.
• Audit a page’s change history to identify when a breaking change was introduced before reverting.
• Delete an unused wiki page after confirming no active references in the repo.