glenux/code-preloader
1
0
Fork 0
Code Issues 19 Pull requests Projects 1 Releases Packages Wiki Activity

Compare commits

base: glenux:7ff161f4ee9c2b3eb1b8e449d7582e87d3c775bd
Branches Tags
glenux:develop
glenux:feature/issue/9-add-support-for-jinja-template
glenux:master
..
compare: glenux:a53ae57f51fac8efaa5f222571ae1c7a7aec0b51
Branches Tags
glenux:develop
glenux:feature/issue/9-add-support-for-jinja-template
glenux:master

4 commits
7ff161f4ee ... a53ae57f51

Author SHA1 Message Date
Glenn
a53ae57f51 Merge branch 'develop' of code.apps.glenux.net:glenux/code-preloader into develop
Some checks failed
continuous-integration/drone/push Build is failing
Details
2024-01-04 22:55:33 +01:00
Glenn
46ef698224 fix: add missing patch for jinja 2024-01-04 22:54:32 +01:00
Glenn
3c28d5eace refactor: move docs/ to misc/logo/ 2024-01-04 22:53:38 +01:00
Glenn
3f75ccca34 refactor: move prompts/ to misc/ 2024-01-04 22:53:21 +01:00
7 changed files with 24 additions and 18 deletions
Show stats Expand all files Collapse all files

0
docs/logo.svg → misc/logo/logo.svg
View file

10
misc/prompts/request-crinja.txt Normal file
View file

@ -0,0 +1,10 @@
I would like to replace the hardcoded structure of the output "@@ ... " with a jinja template that would be handler with the crinja.cr shard.
My strategy is to preload the content during process_file and store it in a hash.
Then the hash will be used in the end to render a final template (from crinja).
Can you please tell me :
* where the changes should occur (which file? which class? which method?)
* what kind of changes must be made there?
Please do not write code yet, simply explain.

7
misc/prompts/request-improve-readme1.txt Normal file
View file

@ -0,0 +1,7 @@
We want to improve the README.md file as for an open-source project following the best practices.
Please focus on the code provided in the « @@ File ... » sections and analyze the existing « @@ File "README.md" », then take in account the content of class Config which analyzes the command line.
In this analysis of the existing « @@ File "README.md" », please provide me with a list of things that you appreciate, a list of things to amplify, a list of things to adjust.

7
misc/prompts/request-improve-readme2.txt Normal file
View file

@ -0,0 +1,7 @@
We want to improve the README.md file as for an open-source project following the best practices.
Please focus on the code provided in the « @@ File ... » sections and analyze the existing « @@ File "README.md" », then take in account the content of class Config which analyzes the command line.
Please concentrate on the detail of your analysis in your previous message and write a new improved/fixed version of « @@ File "README.md"

2
prompts/request-subcommand.txt → misc/prompts/request-subcommand.txt
View file

@ -1,5 +1,3 @@
@@REQUEST
I would like to change CLI parameters structure add add two subcommands: I would like to change CLI parameters structure add add two subcommands:
* init : which will create an example .code_preloader.yml file (with comments) * init : which will create an example .code_preloader.yml file (with comments)
* pack : which will create the packed version of the current directory for LLM prompting * pack : which will create the packed version of the current directory for LLM prompting

0
prompts/footer.txt → misc/prompts/request.txt
View file

16
prompts/footer-improve-readme.txt
View file

@ -1,16 +0,0 @@
@@ REQUEST (ANALYZE)
We want to improve the README.md file as for an open-source project following the best practices.
Please focus on the code provided in the « @@ File ... » sections and analyze the existing « @@ File "README.md" », then take in account the content of class Config which analyzes the command line.
In this analysis of the existing « @@ File "README.md" », please provide me with a list of things that you appreciate, a list of things to amplify, a list of things to adjust.
@@ REQUEST (WRITE)
We want to improve the README.md file as for an open-source project following the best practices.
Please focus on the code provided in the « @@ File ... » sections and analyze the existing « @@ File "README.md" », then take in account the content of class Config which analyzes the command line.
Please concentrate on the detail of your analysis in your previous message and write a new improved/fixed version of « @@ File "README.md"