Compare commits
No commits in common. "a53ae57f51fac8efaa5f222571ae1c7a7aec0b51" and "7ff161f4ee9c2b3eb1b8e449d7582e87d3c775bd" have entirely different histories.
a53ae57f51
...
7ff161f4ee
7 changed files with 18 additions and 24 deletions
|
@ -1,10 +0,0 @@
|
|||
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.
|
|
@ -1,7 +0,0 @@
|
|||
|
||||
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.
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
|
||||
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"
|
||||
|
16
prompts/footer-improve-readme.txt
Normal file
16
prompts/footer-improve-readme.txt
Normal file
|
@ -0,0 +1,16 @@
|
|||
@@ 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"
|
||||
|
|
@ -1,3 +1,5 @@
|
|||
@@REQUEST
|
||||
|
||||
I would like to change CLI parameters structure add add two subcommands:
|
||||
* 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
|
Loading…
Reference in a new issue