Skip to content

Wiki & Knowledge Commands

Access community knowledge bases and information resources.

Tip: Use !ask <question> for a unified search across wiki, outline docs, RSS links, Q&A history, Wikipedia, and more. The commands below search individual sources directly.

Display wiki links and information.

!wiki

Response: Shows links to IrregularPedia and how to contribute.


Search the wiki for content.

!wikisearch <query>
!ws <query>

Example:

!ws operational security

Response: Returns matching wiki articles with summaries and links.


AI-powered Q&A from wiki content.

!wikiask <question>
!wa <question>

Example:

!wa What are the best practices for secure communications?

Features:

  • Searches wiki for relevant articles
  • Uses AI to synthesize an answer
  • Provides source links

Show wiki index or categories.

!wikiindex

Display wiki statistics.

!wikistats

Turns a chat message into a wiki entry and opens a merge request. Nothing goes live until the MR is merged. Any member can use it by replying to a message. An admin’s reply run merges by itself once its pipeline passes; a member’s run, and any -n run, goes to the admins, who approve or reject it in Signal.

!wikiadd # As a reply: use the replied-to message
!wikiadd -n 50 # Admins: use the last 50 messages in this group (max 200, groups only)
!wikiadd -n 50 -t "OSINT" # Admins: hint the topic to steer placement
!wikiadd -h # Show help (never runs the command)

Your MR on GitLab: if your Signal is linked to your IrregularChat account (!linkme) and you have signed in to GitLab once, the merge request is assigned to you and says you requested it. Otherwise it opens unassigned, and the bot tells you how to link.

What the reply shows: each changed page, labelled from the change itself:

  • 🆕 New page: the page did not exist
  • ➕ Addition: lines added to an existing page, none removed
  • ✏️ Modification: an existing page lost or changed lines

Each page has a link and a one-line AI summary of what was added.

How it works:

  1. The bot collects the messages (the reply, or the most recent N) and drops !commands. A picture counts as a message even with no caption: up to four images are read by the community AI (never cloud AI, metadata removed first), and their text, such as a feature list on a slide, joins the message. Images take about a minute each.
  2. It opens up to three links found in the messages and reads the pages, so the entry says what the resource actually is instead of guessing from the URL
  3. The AI sees every existing wiki page and the most related ones in full, and either adds a section to an existing page or creates a new page
  4. The bot writes the change on a branch, pushes it, and opens a merge request against the monorepo, assigned to you when your GitLab account is confirmed
  5. If you are a bot admin and replied to a message, the bot merges it itself: GitLab merges it once its pipeline passes (about 5 minutes). An admin’s -n run is not merged automatically: nobody has read the write-up of those messages yet, so it gets a review card like a member’s
  6. If you are a member, the admins get a review card in Signal (a DM, or the admins’ review group if one is set) with the summary, a short preview, related wiki pages and related shared links (the same links !search finds). An admin answers with !wikiapprove or !wikireject, and you get a DM with the outcome
  7. After the merge, irregularpedia.org rebuilds within a couple of minutes

Safety and quality rules:

  • Any member, by reply; -n (recent group history) is admin-only because it reads other people’s messages
  • 5 runs per hour per person, and members together can open at most 25 wiki MRs a day
  • Not available in rooms where AI is turned off (!room ai off)
  • Names, handles and anything resembling a credential are left out; a secret scan blocks the write if one slips through
  • An existing page is never overwritten: a new page whose name is taken becomes a section on that page, and a section the page already has is skipped
  • Entries state facts directly — no hedging — and only what the messages or linked pages support
  • New pages get a one-line description; the MR checklist flags new pages whose folder is not in the sidebar
  • The bot merges only an MR it opened itself: open, from a wikiadd/ branch to main, whose latest commit the bot pushed, and which changes only wiki pages (.md/.mdx under the wiki content folder, no deletes or renames). The merge is pinned to that commit, so a later push stops it. Anything else is refused and reviewed on GitLab

What gets skipped: jokes, banter, greetings, unanswered questions, unsupported opinions, and anything the wiki already covers.

Requirements:

  • GITLAB_WIKI_TOKEN (Developer access on the monorepo is enough — the bot opens MRs, it never pushes to main)
  • GITLAB_WIKI_MERGE_TOKEN for merging from chat (see the configuration reference). Without it, nothing merges from chat and admins merge on GitLab as before
  • An AI provider (the bot tries local AI, then Mistral, then OpenAI)

!wikiapprove (Approve a Wiki MR) — admin only

Section titled “!wikiapprove (Approve a Wiki MR) — admin only”

Approves a member’s !wikiadd merge request. The bot merges it once its pipeline passes, and the member gets a DM.

!wikiapprove # List the wiki MRs waiting for review
!wikiapprove 517 # Approve MR !517
!wikiapprove # As a reply to a review card: approve that MR

Only MRs the bot opened, whose commits the bot pushed and which change only wiki pages are merged; anything else is left for review on GitLab.


!wikireject (Reject a Wiki MR) — admin only

Section titled “!wikireject (Reject a Wiki MR) — admin only”

Closes a member’s !wikiadd merge request and tells them why.

!wikireject 517 Already covered on the OSINT page # Reject MR !517 with a reason
!wikireject Already covered on the OSINT page # As a reply to a review card

The reason is posted on the MR and sent to the member.

Outcome DMs are best-effort: the bot remembers who asked only in memory, so after a bot restart the member is not told.


Show forum links and information.

!forum

Response: Links to community Discourse forum.


Display important community links.

!links

Response: Curated list of community resources, tools, and references.


Show frequently asked questions.

!faq

Response: Common questions and answers about the community.


Display documentation links.

!docs

Response: Links to technical documentation and guides.


Show upcoming community events.

!events
!events search <term>

Response: Calendar of upcoming events with RSVP counts and poll status.

See: Events for full documentation including !event quick, !event parse, !event plan, !vote, and !rsvp commands.


Create a new forum post from Signal.

!fpost <title> | <content>
!fpost # Reply to message to use as content

Example:

!fpost Security Discussion | Let's talk about recent developments...

Show latest forum posts.

!flatest

Response: Recent posts from Discourse with titles and links.


Search forum posts.

!fsearch <query>

Example:

!fsearch vpn recommendations

List forum categories.

!categories

Response: Available Discourse categories for posting.


VariableRequiredDescription
DISCOURSE_URLFor forumDiscourse instance URL
DISCOURSE_API_KEYFor forumDiscourse API key
DISCOURSE_USERNAMEFor forumBot’s Discourse username
DISCOURSE_QA_CATEGORYNoCategory ID for Q&A posts (default: 5)

Recent changes

  1. fix(wikiadd): read images, take the most recent -n messages, show the AI's reason gitayam
  2. feat(wikiadd): admin auto-merge, Signal review, change summaries gitayam
  3. docs(wiki): !wikiadd is open to members by reply gitayam
  4. docs(signal-bot): rewrite !wikiadd docs for the MR flow Sac
  5. refactor(structure): flatten workers into apps/ directory gitayam