# Using command and shell modules properly

**URL:** <https://forum.ansible.com/t/using-command-and-shell-modules-properly/22600>\
**Category:** Ansible Project\
**Tags:** ansible-lint\
**Created:** [September 21, 2016, 12:40pm UTC](https://forum.ansible.com/t/using-command-and-shell-modules-properly/22600 "2016-09-21T12:40:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![willthames](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@willthames](https://forum.ansible.com/u/willthames)\
**Post date:** [September 21, 2016, 12:40pm UTC](https://forum.ansible.com/t/using-command-and-shell-modules-properly/22600/1 "2016-09-21T12:40:47Z")

</div>

As I say in the intro to the post, I have strong opinions on using command and shell properly - most of those opinions are encoded into ansible-lint checks.

Would be interested in any feedback, particularly anything that could be done better with command/shell that I’ve missed.

[http://willthames.github.io/2016/09/21/using-command-and-shell-in-ansible.html](http://willthames.github.io/2016/09/21/using-command-and-shell-in-ansible.html)

Will

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [September 21, 2016, 2:42pm UTC](https://forum.ansible.com/t/using-command-and-shell-modules-properly/22600/2 "2016-09-21T14:42:43Z")

</div>

Looks great!.

Not sure how i feel about the term ‘Ansibley’ though …
