I don't have anything in Russian, though there are some very good Russian ROM hackers. https://gbx.ru http://www.magicteam.net/
being two links good to start with. Something there might be useful.
There are some programs that are scripting languages, or have plugin support. You can often program these to do what you want without having to make a full program to do it yourself.http://www.romhacking.net/?page=utilities&category=21&platform=&game=&author=&os=&level=&perpage=20&title=&desc=&utilsearch=Go
has many programs for extracting things, and many will have source code you can look at.http://www.romhacking.net/utilities/779/
is an example of a scripting program, though do read the license it comes with.
Generally though files have a few aspects
1) Any kind of file details, including names of things it contains.
3) Data itself.
Unpacking is typically using the pointers to locate the files and then slicing off each part of the data section into its own file. If the game does not have pointers we have seen some programs do detection methods for things (some GBA editors, Golden Sun ones, being among the more noted). If there is compression then that too.
You can do a crude version of this without much programming skill. I like a program called filecutter ( https://web.archive.org/web/20170218180937/http://min.midco.net/cracker/filecutter.zip
) but there are others. With that you can tell it to slice this many bytes out at this point in the file. Make a batch file containing a few hundred commands and you have your extraction script for that file at least. For a ROM that will be the same for everybody and same forever then that is not so bad. You can get the locations and lengths from the pointers which a hex editor can dump (if you know a pointer and the next pointer you can subtract and get length, assuming length is not there as part of it all).
Neither of those are Russian but my usual two links for people wanting to learn general programming and not assembly. Hopefully you can find a translation of some of those books mentioned (many have them to many languages).
If the additional file details are relevant you probably want to note them as well. For instance sound files might note what volume to play things, what instruments to use, what speed to play things and a few other things like that.
Also if you aim to one day repack them you will likely want to note any relevant information, file ordering or the like that simple files might not have to use to recreate the file so it works with the game.
There are hundreds of arrangements of parts of files just for a basic archive, and hundreds of little quirks. For instance in one case on the DS I had a file format that shifted its numbers (effectively multiplied them by 4) for reasons best known to itself. Another common DS archive format called NARC has the high bits of its pointers set if the file is a subdirectory within the archive. This sort of thing can take a long time to learn and to spot, however it is pretty much the definition of what ROM hacking is.
For examples of formatshttp://www.romhacking.net/documents/469https://wiki.multimedia.cx/index.php?title=Category:Game_Formatshttp://wiki.xentax.com/index.php/Game_File_Format_Centralhttps://sites.google.com/site/kiwids/sdat.htmlhttp://kiwi.ds.googlepages.com/nsbmd.htmlhttps://wiki.vg-resource.com/Nitro_Files
Several of those pages will use a format to describe the contents based around what C programmers will use so might want to learn that even if you don't learn/use C in your extraction program.