Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

wiki

Estrelas0

Forks0

Atualizado14 de julho de 2026 às 23:58

Maintain an in-repo markdown wiki under wiki/: init a new wiki, surgically update it after code changes, or answer questions from it. Use for /wiki init, /wiki update, /wiki ask, "generate the wiki", "refresh the docs", "how does X work in this repo" when wiki/ exists, deep-wiki style docs, or keep the wiki in sync — never wipe an existing wiki; prefer small incremental edits. Also use when installing CI that runs wiki update on push.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

manojbajaj95

manojbajaj95/skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

12 arquivos

SKILL.md

readonly

id	1288e770-c01e-476c-b985-f8a4cce53a94
name	wiki
description	Maintain an in-repo markdown wiki under wiki/: init a new wiki, surgically update it after code changes, or answer questions from it. Use for /wiki init, /wiki update, /wiki ask, "generate the wiki", "refresh the docs", "how does X work in this repo" when wiki/ exists, deep-wiki style docs, or keep the wiki in sync — never wipe an existing wiki; prefer small incremental edits. Also use when installing CI that runs wiki update on push.
disable-model-invocation	true

Wiki

In-repo markdown wiki under wiki/. Three triggers — pick one from the user request:

Trigger	When	Reference
init	No usable `wiki/` yet; user asks to create/generate/bootstrap the wiki	references/init-and-update.md (init path) + references/structure-and-format.md
update	`wiki/` exists; user asks to refresh/sync/update after code changes	references/init-and-update.md (update path) + references/structure-and-format.md
ask	User asks how/where/why about the repo and `wiki/` should be the primary source	references/ask.md
install	User asks to refresh wiki automatically and keep wiki up to date	references/install.md.

Hard rules

Never wipe an existing wiki/. If it exists with real content, use update (even if the user said "generate" or "rebuild"). Only init when there is no usable wiki.
Prefer small surgical edits on update. No formatting-only churn. No-op is success when nothing relevant changed.
Respect .wikiignore at repo root and all .gitignore patterns — never read excluded paths. See references/wikiignore.md.
Never read or document secrets, credentials, or .env files (.env.example placeholders are OK).

Init (summary)

If wiki/ already has content → switch to update.
Survey the repo (targeted, not every file).
Write wiki/_plan.md (pages, evidence, open questions).
Execute the plan using toc-and-layout.md and page-writing.md.
Assemble: listings, root log.md, .wiki-meta.json.
Ensure top-level AGENTS.md / CLAUDE.md keep a short wiki pointer (agents-pointer).
Write repo-root .wikiignore when missing (wikiignore).
Delete wiki/_plan.md. Report what was created.

Update (summary)

Diff against .wiki-meta.json commitHash (and uncommitted changes).
Soft budget: few source files changed → touch few wiki pages; skip cosmetic edits.
Optional short wiki/_plan.md for the edit list; delete it when done.
Edit in place. Refresh listings/log.md/meta only if content changed.
Keep the AGENTS/CLAUDE wiki pointer present (agents-pointer).
If nothing relevant changed, leave every file untouched and say the wiki is current.

Ask (summary)

Answer from wiki/ first; cite pages; verify source only when the wiki looks stale or incomplete. See ask.md.

Output

wiki/ with concept pages (frontmatter + type), listing index.md files, root log.md, and .wiki-meta.json. Plus a short pointer in top-level AGENTS.md and/or CLAUDE.md.

Mais deste repositório

mesmo repositório

engineering-principles

manojbajaj95/skills

Apply shared engineering principles (YAGNI, deep modules, trusted libraries, separation of concerns, leave it better) when writing or changing code, or when drafting CONTRIBUTING.md. Use whenever the user asks for design guidance, contribution guidelines, how to structure changes, or to follow project engineering principles — even if they do not name this skill.

2026-07-140

setup

manojbajaj95/skills

Initialize or scaffold a repository with standardized project baselines (README, license, tests, lint/types, AGENTS.md, pre-commit, CI, skills). Use when the user asks to set up a new repo, bootstrap project tooling, or apply your standard repo setup — not for routine feature work or code review. Prefer this skill whenever they say "set up this repo", "scaffold", "initialize the project", or want release-please / pre-commit / PyPI trusted publishing as part of initial setup.

2026-07-140

id	1288e770-c01e-476c-b985-f8a4cce53a94
name	wiki
description	Maintain an in-repo markdown wiki under wiki/: init a new wiki, surgically update it after code changes, or answer questions from it. Use for /wiki init, /wiki update, /wiki ask, "generate the wiki", "refresh the docs", "how does X work in this repo" when wiki/ exists, deep-wiki style docs, or keep the wiki in sync — never wipe an existing wiki; prefer small incremental edits. Also use when installing CI that runs wiki update on push.
disable-model-invocation	true

Wiki

In-repo markdown wiki under wiki/. Three triggers — pick one from the user request:

Trigger	When	Reference
init	No usable `wiki/` yet; user asks to create/generate/bootstrap the wiki	references/init-and-update.md (init path) + references/structure-and-format.md
update	`wiki/` exists; user asks to refresh/sync/update after code changes	references/init-and-update.md (update path) + references/structure-and-format.md
ask	User asks how/where/why about the repo and `wiki/` should be the primary source	references/ask.md
install	User asks to refresh wiki automatically and keep wiki up to date	references/install.md.

Hard rules

Never wipe an existing wiki/. If it exists with real content, use update (even if the user said "generate" or "rebuild"). Only init when there is no usable wiki.
Prefer small surgical edits on update. No formatting-only churn. No-op is success when nothing relevant changed.
Respect .wikiignore at repo root and all .gitignore patterns — never read excluded paths. See references/wikiignore.md.
Never read or document secrets, credentials, or .env files (.env.example placeholders are OK).

Init (summary)

If wiki/ already has content → switch to update.
Survey the repo (targeted, not every file).
Write wiki/_plan.md (pages, evidence, open questions).
Execute the plan using toc-and-layout.md and page-writing.md.
Assemble: listings, root log.md, .wiki-meta.json.
Ensure top-level AGENTS.md / CLAUDE.md keep a short wiki pointer (agents-pointer).
Write repo-root .wikiignore when missing (wikiignore).
Delete wiki/_plan.md. Report what was created.

Update (summary)

Diff against .wiki-meta.json commitHash (and uncommitted changes).
Soft budget: few source files changed → touch few wiki pages; skip cosmetic edits.
Optional short wiki/_plan.md for the edit list; delete it when done.
Edit in place. Refresh listings/log.md/meta only if content changed.
Keep the AGENTS/CLAUDE wiki pointer present (agents-pointer).
If nothing relevant changed, leave every file untouched and say the wiki is current.

Ask (summary)

Answer from wiki/ first; cite pages; verify source only when the wiki looks stale or incomplete. See ask.md.

Output

wiki/ with concept pages (frontmatter + type), listing index.md files, root log.md, and .wiki-meta.json. Plus a short pointer in top-level AGENTS.md and/or CLAUDE.md.