A fast and convenient tool for creating files
crt is a powerful command-line tool designed for quick and easy file creation, as well as generating projects based on predefined templates. It helps you save time and boost productivity by eliminating the need to manually create files and organize structures.
Features
- File creation: instantly create files using simple commands.
- Folder creation: easily create nested directory structures.
- Template support: use and create templates for common projects and file types.
- Template management: create, view, delete, and rename custom templates.
- Flexibility: easily customize templates to fit your needs.
Commands
- files: create files, folders, and nested structures.
- temps: create a project using a template.
Command Description
File and Folder Creation
Accepts a string with file and folder names (wrap the string in quotes ""). Use : to separate items, and <> to define folders.
crt {file_name} {extension}
Template Management
| Command | Description |
|---|---|
crt -v |
View all available templates |
crt -t {name} |
Apply an existing template |
crt -t {name} -f |
Apply a template with content filling |
crt -t {name} -p {path} |
Specify target directory for template creation |
crt -t {name} --append |
Create a new template from the current directory |
crt -t {name} --remove |
Delete an existing template |
crt -t {name} --rename {new_name} |
Rename a template |
.gitignore Generation
| Command | Description |
|---|---|
crt -t gitignore py |
Create .gitignore for Python |
crt -t gitignore js |
Create .gitignore for JavaScript/Node.js |
crt -t gitignore java |
Create .gitignore for Java |
crt -t gitignore c |
Create .gitignore for C |
crt -t gitignore c++ |
Create .gitignore for C++ |
crt -t gitignore c# |
Create .gitignore for C# |
crt -t gitignore go |
Create .gitignore for Go |
Installation
pip install crtfiles
---> 100%
Examples
Templates
1) View Available Templates
crt -v
--->
Available templates:
Default:
• postgres (12 files)
• fastapi (22 files)
• react (71 files)
• tg_bot (19 files)
• tg_bot_full (96 files)
• gitignore (py, js, java, c, c++, go, c#)
2) Create a Custom Template
Navigate to your project directory and run:
crt -t my_template -a -p my_project
--->
your_folder/
│
├── lib/
│ ├── screens/
│ ├── widgets/
│ ├── models/
│ ├── services/
│ ├── utils/
│ ├── assets/
│ └── main.py
│
├── test/
├── build/
├── README.md
└── .gitignore
3) Apply Template with Content Filling
crt -t fastapi -p my_app -f
--->
Template 'fastapi' applied successfully to: .\\my_app
4) Apply Template Without Content (Structure Only)
crt -t fastapi -p my_app
--->
Template 'fastapi' applied successfully to: .\\my_app
5) Rename a Custom Template
crt -t my_template -rn my_temp
--->
Template renamed: 'my_template' → 'my_temp'
6) Delete a Custom Template
crt -t my_template -rm
--->
Template 'my_template' removed successfully!
Files
1) Create Files
crt main.py:test.py:requirements.txt
--->
your_folder/
│
├── main.py
├── test.py
└── requirements.txt
2) Create Files with Extension
crt main:test py
--->
your_folder/
│
├── main.py
└── test.py
3) Create Folders
crt "src<>:image<>:models<>"
--->
your_folder/
│
├── src/
├── image/
└── models/
4) Create Nested Folders
crt "src<models<>:assets<>>:lib<models<>>"
--->
your_folder/
│
├── src/
│ ├── models/
│ └── assets/
│
└── lib/
└── models/
5) Create Nested Files Inside Folders
crt "app<base.py:control.py>:backends<database<models.py>:base.py>"
--->
your_folder/
│
├── app/
│ ├── base.py
│ └── control.py
│
└── backends/
├── database/
│ └── models.py
└── base.py
.crtignore Configuration
To exclude files and folders from templates, create a .crtignore file in the project root.
Example .crtignore
__pycache__
.venv
venv
.git
.env
*.log
*.tmp
.DS_Store
Thumbs.db
Note
If you are using Windows CMD, wrap the input string in quotes "" to avoid conflicts with folder creation symbols <>.
Feedback
I’m always happy to hear your feedback and suggestions for improving crt.
- Email: feed619pro@gmail.com
Metadata
Release files for crtfiles 2.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| crtfiles-2.0.5.tar.gz | 1.0 MB | Without provenance | Details for crtfiles-2.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| crtfiles-2.0.5-py3-none-any.whl | Python 3 | none | any | Details for crtfiles-2.0.5-py3-none-any.whl |
Total release size: 2.0 MB
Release files / crtfiles-2.0.5.tar.gz
| Download URL | crtfiles-2.0.5.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b3bec5cef648fd36d64a76a76f5b3623ff5dcfee6831ccc9e308fb6b14125d2
|
|
BLAKE2b-256 checksum How to use checksums |
48d8ffe3596cd0ce030aa58fd3a34bb28dd0b8ff3962bc7d93d54351e9a4681b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Release files / crtfiles-2.0.5-py3-none-any.whl
| Download URL | crtfiles-2.0.5-py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6136f89d375bd7dfca3ec72934e280b9b5b154ee6887875e89302ec82ad9fbcd
|
|
BLAKE2b-256 checksum How to use checksums |
1a1d4604633220aeb19fcae2efcceab878b991438248c949ac9fcf935dd8e400
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Security for crtfiles 2.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.