MediaWiki talk:XTools-AutoEdits.json

Latest comment: 2 months ago by Titore in topic Growth Team's "Add a link"
XTools AutoEdits configuration
This page is used to request changes to configuration file that controls the XTools AutoEdits tool.

Only tools that are widely used should be included. Every tool added will slow down XTools a tiny bit more, so please be diligent and ensure the list doesn't become overly exhaustive.

Administrator instructions
  • Remember that only tools that are regularly and widely used should be included. Every addition here slows down the queries a tiny bit more. We cannot include any and every tool ever made. Also note that very similar tools can be combined to improve performance; for example the "delsort" tool for en.wikipedia includes multiple tools. You make the judgement call, but feel free to ask for help from other maintainers here if you are unsure.
  • Test your changes before saving. Do this by first updating MediaWiki:XTools-AutoEdits.json/sandbox with the desired changes. Then, login to XTools and append ?usesandbox=1 to any XTools AutoEdits result page to force it to use the sandbox. The easiest way is to test against accounts that have made edits using the tool you're trying to add, and look for contributions using only that tool. The requester should have shared example diffs.

    For example, if you wanted to add the tool "My Fun Tool" to de.wikipedia, which you know has been used by User:Example: Add the definition to the sandbox config, then load the contributions page for just that user and tool, as with:

    From here you can see if the qualifying edits show up. Compare with production (without ?usesandbox=1) as necessary. While you can use the sandbox on a normal /autoedits result page, loading just /autoedits-contributions is significantly faster.

    Note also that the ?usesandbox=1 option will bypass caching, so any changes to the sandbox should take effect immediately. Changes to the production configuration are cached for up to 20 minutes, so be patient for them to take effect.

  • If you need help with testing regex itself, there are some external tools for this such as (just make sure to test against the PCRE flavor, which is the default).
Performance tips
  • Try to keep the regex simple and short without allowing it to be too broad. For example, Huggle edits in English contain ([[WP:HG|HG]]) in the summary but the regex we use is \(\[\[WP:HG, since the piped part of the link isn't needed to safely conclude it is a Huggle edit.
  • Use tags wherever possible as they are significantly more efficient to query. Sometimes you have to include regex to account for edits made before the tag was introduced, in which case you should include both regex and the tag.
  • Restrict to applicable namespaces where possible, especially if the tool is not used in the mainspace or other popular namespaces.

Please try to keep the definitions in the following order, with the entries sorted alphabetically:

  • Global list (nested the key "global")
    • List tools that are used extensively on multiple medium or large wikis. If only used on small wikis, it may be more efficient to list each of those individually for those wikis. Keep in mind any tools added under "global" are run for all wikis, and may unnecessarily slow down XTools on wikis that don't use those tools.
    • These tool definitions may include regular expressions, but should probably also include tags because the regex may not apply to non-English wikis.
    • You can also set wiki-specific regex that will get merged into the global regex (to override for each language, for example).
    • Other local values such as 'link', 'tag' and 'revert' are overridden, not merged into the global value.
    • See "Huggle" under "global" and "" for an example.
  • Per-language list (such as "fr")
    • Key should match the ISO language code. All tools defined here will get ran for projects using that language.
    • These tool definitions generally only include native MediaWiki actions. For these, link to documentation (e.g. mw:Special:MyLanguage/Help:Moving a page for the "Page move" tool).
    • The key should match the local name of the tool, and translations set using "label", along with the language-specific "regex" that goes with that tool.
  • Per-wiki list (such as "")
    • Some definitions are only included to override values of global or per-language definitions.
Format for individual tool definitions

Either beneath "global", the language list (such as "fr") or under a wiki (such as "de.wikisource"), use any the following (only "regex" or "tag" are required):

  • Tool name (such as "Twinkle")
    • "regex" – Regular expression to match against edit summary. This follows PCRE format. Don't forget to escape regex literals using two backslash characters. For instance, to look for the link [[COM:FR|File renamed, you would use \\[\\[COM:FR\\|File renamed. Also shorten regex as much as possible. For example, the edit summary for "Undo" has changed over time – It could start with "undid", "undone" or "[[WP:UNDO|Undid]]", so our regex ends up looking like:
    ^(Undid|Undo|\\[\\[WP:UNDO\\|Undid\\]\\]) revision \\d+ by \\[\\[Special:(Contribs|Contributions)\\/.*?\\|.*?\\]\\]
    • "tags" – Names of tags applied to edits made using the tool, if applicable. See Special:Tags on the applicable wiki for full list.
    • "tag_excludes" – Don't count edits that also use this tag. This is used for example to hide Huggle edits when viewing Rollback edits. There are some known bugs, see phab:T191133. Please be careful using this option and test your changes thoroughly.
    • "link" – Wiki link to tool documentation. Full URLs or external links do NOT work, but interwiki do. Prefer official, multilingual documentation where possible (e.g. mw:Special:MyLanguage/Help:Moving a page instead of local documentation on moving pages). If no link exists, linking to the source code may be enough. If there's nowhere to link, it probably shouldn't be listed.
    • "label" – Text to use as the label for the tool, defaults to the tool's key. Use this for translations.
    • "revert" – If the tool is used only to revert edits (and not also issue talk page notifications, etc.), set this to true. If the tool is merely capable of reverting edits, set 'revert' to regex that would only account for such reverts. See the "Twinkle" entry for an example. The revert-only regex is necessary for the ArticleInfo and elsewhere in XTools, so as to differentiate edits that added content from edits that restored content.[1]
    • "contribs" – Set to true to include edits with the given tool in lists of non-automated contributions. For example, this is done for en.wikipedia's "ProveIt", because that tool often includes prose that was added by the user, and not entirely a semi-automated edit.
    • "namespaces" – The namespace IDs of where the tool is used. This is used to speed up the queries, so please use it where possible. Omit if the tool applies to all or most namespaces.
    • "talk_namespaces" – Set to only target talk namespaces.

For each tool definition, either "regex" or "tag" are required. In some cases you might want to include both, say if older versions of the tool did not add tags to the edits.

Responding to requests
  1. Ensure the tool meets the criteria outlined in the above guidelines.
  2. Test your changes first in the sandbox
  3. Make the changes to the production config.
  4. Mark the request as {{done}}


  1. However, XTools will eventually utilize the "reverted" tag to identify such edits, thus if the tool was introduced after September 2020 (after the "reverted" tag was introduced), it may not be necessary to set this option.
Request that a new (semi-)automated tool be added
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 3 days and sections whose most recent comment is older than 365 days.

Tool addition request

  • Wiki:
  • Name of tool: AntiVandal
  • Links to example edits: [1][2]
  • Link to the tool's documentation or homepage: Wikipedia:AntiVandal

Zippybonzo (talk) 07:57, 1 May 2023 (UTC)Reply

Support as they currently just get added to Generic Rollback it would be great to see the AV edits counted separately. 1AmNobody24 (talk) 07:45, 10 May 2023 (UTC)Reply
@User:1234qwer1234qwer4 Got time to take a look at this? Thanks 1AmNobody24 (talk) 07:53, 16 June 2023 (UTC)Reply
Support - sorry I didn't see this when I made my request The void century (talk) 18:51, 16 June 2023 (UTC)Reply
  • Wiki:
  • Name of tool: Ultraviolet
  • Links to example edits: [3] [4] [5]
  • Link to the tool's documentation or homepage: Wikipedia:Ultraviolet

TheBigBookOfNaturalScience (talk) 03:20, 23 June 2023 (UTC)Reply

PAWS new oauth

  • Wiki: all
  • Nom de l’outil: PAWS
  • Liens vers des exemples de diff: [6]

Thanks Framawiki (talk) 17:46, 24 July 2023 (UTC)Reply

@Framawiki,   added along with another tag that has been heavily used according to Special:Tags on Commons and Wikidata and somewhat on enwiki.
On another note, I can't seem to find the "OAuth CID: 905" and "OAuth CID: 919" tags anywhere, at least on those three wikis and Meta. (The very first one, "OAuth CID: 351", appears to have been barely used, but there are at least some edits with it.) Since the initial list of tags appears to originate from a comment by @AntiCompositeNumber, could I have some clarification on these? Right now these two seem a bit like clutter that's eating system resources (particularly since this is a "global" tool, being checked on every wiki). ~~~~
User:1234qwer1234qwer4 (talk)
20:58, 14 September 2023 (UTC)Reply
@1234qwer1234qwer4. Thanks. As far I know, when developer of an app using oauth needs to update its app to change the rights requested on the behalf of the user, he needs to create a new version. New oauth customer version creates a new tag ID, and the previous one is no longer used from now. Ie phab:T338023 created a new oauth customer, so all paws edits done from this time are using the new tag ID. Framawiki (talk) 22:24, 14 September 2023 (UTC)Reply

Add Checkty as a semi-automated tool on hewiki


Checkty is an editing tool widely used on the Hebrew Wikipedia. It allows users to make automated edits like the removal of trailing whitespaces, fixing common grammar mistakes, assuring consistency in the placement of punctuation marks relative to adjacent references, etc.

It is the second-most popular gadget on the Hebrew Wikipedia. Having been around since 2009, edits made using Checkty are automatically marked with the צ'קטי tag since August 2015. Since that time, more than 300 thousand edits have been made with this gadget.

Checkty is a very useful tool. However, due to its simplicity and easiness to use, it frequently has the effect of making dozens (sometimes hundreds) of consecutive bot-like edits. While not a completely automatic tool, it often requires very little, if any, manual intervention by the editor. Many of the Hebrew Wikipedia editors with the largest number of edits have made a significant portion of their edits with Checkty, and it would therefore be very useful and informative to have this data included on XTools' AutoEdits interface.

As mentioned, all edits made with this gadget are tagged, so you can easily access the list of recent changes made with it.

Thanks, Guycn2 (talk) 22:18, 25 September 2023 (UTC)Reply

Requesting addition of RefRenamer to


Thank you!

Cl3phact0 (talk) 16:36, 20 October 2023 (UTC)Reply

Tracking of moreIdentifiers for Wikidata?


This is a (customizable) script that can import missing external identifiers from VIAF to Wikidata. The statistics of usage can be checked here:Wikidata:Database reports/Gadget usage statistics/wikidata PKalnai (talk) 17:55, 3 December 2023 (UTC)Reply

Recognizing OpenRefine version 3.7?


Edits by OpenRefine on PAWS, currently in version 3.7, are not recognized by XTools as (semi-)automated. Is it possible to update the configuration, please? I believe the tool is widely used and its statistics are relevant. Example of such edit: [7] PKalnai (talk) 22:11, 14 December 2023 (UTC)Reply

Add Wikiplus to English Wikipedia


The Master of Hedgehogs (talk) 17:47, 10 March 2024 (UTC)Reply

Add afcrc-helper to English Wikipedia


I Am Andumé (talk) 02:40, 13 March 2024 (UTC)Reply

Growth Team's "Add a link"


Unlike other Newcomer Tasks, these edits are machine suggested in a way that users just have to choose "Yes" or "No". Such semi-automated edits are tagged with newcomer task add link. Titore (talk) 19:05, 4 May 2024 (UTC)Reply

Return to "XTools-AutoEdits.json" page.