wiki

Manage a local GitHub Wiki clone for reading and writing documentation.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/madhavmadupu/atlas-mobile --skill wiki-madhavmadupu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki
Source: https://github.com/madhavmadupu/atlas-mobile/tree/main/.agent/skills/wiki
Command: npx skills add https://github.com/madhavmadupu/atlas-mobile --skill wiki-madhavmadupu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a streamlined way to access, manage, and update your local clone of a GitHub Wiki, ensuring you have the latest architectural and design documentation readily available.

Core Features & Use Cases

  • Read Wiki Content: Access architecture, design docs, and guides.
  • Update Documentation: Make changes to wiki pages locally.
  • Check Status: View the current state of the wiki clone, including unpushed changes.
  • Push Changes: Safely push local wiki updates to the remote repository after explicit user approval.

Quick Start

Use the wiki skill to read the file 'setup-guide.md' from the local wiki clone.

Frequently Asked Questions about wiki

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

FAQPage Schema
How do I manage a local clone of my GitHub Wiki?

You can manage a local GitHub Wiki clone by using Git command-line tools to clone, pull, and commit changes to the `docs/wiki/` directory, ensuring your local architecture documentation stays synchronized with the remote repository.

How do I read and update architecture documentation from a GitHub Wiki locally?

Reading and updating architecture documentation from a GitHub Wiki locally involves cloning the wiki to your `docs/wiki/` directory. You can then edit the markdown files directly and commit the changes to save your updates locally before pushing them to the remote repository.

Do I need Git installed to clone and update GitHub Wiki documentation?

Yes, Git command-line tools are required to clone, pull, and commit changes to your local GitHub Wiki documentation. The Skill operates on the `docs/wiki/` directory and needs local repository access to manage architectural and design documents.

What is the best way to check the status of unpushed changes in a local GitHub Wiki clone?

The best way to check the status of unpushed changes in a local GitHub Wiki clone is to run a status check on the `docs/wiki/` directory. This displays the current state of your local documentation, including any modifications not yet pushed to the remote repository.

How do I push local wiki updates to the remote GitHub repository safely?

To push local wiki updates to the remote GitHub repository safely, you commit your changes to the local clone and then execute a push operation after explicit user approval. This ensures that updates to your design documents are intentionally reviewed before being uploaded.