The tag alias #15808 skirt_up -> skirt_lift has been rejected.

Reason: skirt_up is essentially just skirt_lift with some weirdly specific rules attached to its usage which aren't even being followed most of the time. It has a pretty low post count too, so not many people are even using or searching for it.

EDIT: This tag alias is pending automatic rejection in 5 days.

EDIT: This tag alias has been rejected because it was not approved within 60 days.

EDIT: The tag alias skirt_up -> skirt_lift (forum #155333) has been rejected by @DanbooruBot.

Skirt lift is supposed to be for when the skirt is actively being lifted by someone or something, whereas skirt up is supposed to be for situations where it is not.

That's how I've always interpreted it, at any rate. And the wikis support this distinction.

Not necessarily. Most *_lift and *_pull tags are used for both actively and passively moved clothing, despite what the wikis claim. That's why lifted by self has become a thing.

Dealing with every possibility would basically mean splitting skirt lift into four tags:

• lifting own skirt (actively lifting one's own skirt)
• lifting another's skirt (actively lifting another person's skirt)
• lifted skirt (a passively lifted skirt)
• skirt lift (umbrella tag for all of the above)

This would give us more precision, but I don't know if it's worth the trouble.

It should be noted as well that we've already aliased shirt up to shirt lift and panties down to panty pull.

Wouldn't 1 and 2 be covered with skirt_lift lifted_by_self and skirt_lift lifted_by_another (with some false positives)?

Pretty much. These lifted by self / lifted by another tags are a little inconsistent with what we're doing everywhere else though. See *_own_* versus *_another's_*. Everywhere else we're using combo tags to make this "self versus another" distinction.

This tag alias is pending automatic rejection in 5 days.

This tag alias has been rejected because it was not approved within 60 days.

The tag alias skirt_up -> skirt_lift (forum #155333) has been rejected by @DanbooruBot.