Once you have a directory for your homegrown commands you can try this...
I wrote a command that takes the project I am working on and makes it a callable command.
I usually work in a different directory than the one I have appended to PATH so it has proved much easier to simply call this command instead of typing the entire path to my script directory. I like to keep the languages separate, and I bounce around a bit so I just added a second argument defining the type of script it is.
bash: ungaunga: command not found
# advcomm ungaunga b
case "$2" in
"b") chmod +x $1 && cp $1 /dir/to/scripts/bash/;;
"c") cp $1 /dir/to/scripts/c/;;
"p") cp $1 /dir/to/scripts/perl/;;
"py") chmod +x $1 && cp $1 /dir/to/scripts/python/;;
"r") cp $1 /dir/to/scripts/ruby/;;
"l") cp $1 /dir/to/scripts/lua/;;
*) echo -e "\nusage: `basename $0` sets command as callable\n: b bash : c C : p perl : py python : r ruby : l lua : \n";;