command arguments format not standardised across application

[samuelory]

some commands like add put slash at end of prefix, whereas some like promotion put slash at the start of prefix. this could be confusing for users.

[soc-se-bot]

Team's Response

We admit that we should be more consistent with our command format, but from user's perspective, the program will not cause problem as long as they follow the syntax, which we have provided in UG and help command.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: making it so that the commands all have a slash in front or all behind does not take that much effort, so as per the website it should not be classified as not in scope.

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** As someone who had to constantly rewrite commands because of its inconsistency, i feel that it is inconvenient to have to constantly refer back to the UG/help command just so that i can check if the slash is supposed to be in front or behind of the command. I don't feel like this issue is uncommon as all users of this product would have to type commands, so some of them, especially new users, would inevitably be inconvenienced by having to constantly refer back to the UG/help command. 

---