@snelusha/noto 0.2.3 → 0.3.1

package/README.md

@@ -1,6 +1,6 @@
-<h1 align="center">✨ Noto</h1>
+<h1 align="center">noto ✨</h1>
 <p align="center"><sup>(/nōto/, <em>notebook</em> in Japanese)</sup></p>
-<p align="center">Generate clean commit messages in a snap! ✨</p>
+<img src="https://github.com/snelusha/static/blob/main/noto/banner.png?raw=true" align="center"></img>
 
 <pre align="center">
   <p>npm install -g <b>@snelusha/noto</b></p>

package/dist/cli.cjs

@@ -156,7 +156,14 @@ async function generateCommitMessage(diff) {
     messages: [
       {
         role: "system",
-        content: "You are tasked with generating a Git commit message based on the following staged changes across multiple files. Identify only the key changes and generate a concise commit message in the format: <type>: <description>. The commit message must be a single line, in all lowercase, without a scope or body, and no full stops at the end. Use one of these types: feat, fix, refactor, docs, test, or chore. Do not mention file names unless a file was renamed or is essential to understanding the change. Focus on the most important change, and the message must not exceed 72 characters."
+        content: `You are tasked with generating a Git commit message for the following staged changes across multiple files. Strictly follow the instructions given below to generate the commit message. The instructions are given according to order of importance, as such, make sure each instruction is followed before moving on to the next. Likewise, make sure all instructions are followed successfully.
+          - Ensure the description is written in the present-tense(start with a present tense verb such as add, fix, update, remove, improve, implement, etc...) (IMPORTANT! follow this for java repositories as well).
+          - Identify the key changes only and generate a detailed but brief commit message in the format "<type>: <description>".
+          - Use one of these types: feat, fix, refactor, docs, test, or chore.
+          - The commit message must be a single line, in all lowercase, without a scope or body, and no full stops at the end.
+          - Ensure the message does not exceed 72 characters.
+          - Do not mention file names unless a file was renamed or is essential for understanding the changes.
+          - Focus on the most important changes.`
       },
       {
         role: "user",
@@ -168,7 +175,7 @@ ${diff}`
   return message.text.trim();
 }
 
-const version = "0.2.2";
+const version = "0.3.1";
 
 yargs__default(helpers.hideBin(process.argv)).scriptName("noto").usage("$0 [args]").command(
   "config",

package/dist/cli.mjs

@@ -144,7 +144,14 @@ async function generateCommitMessage(diff) {
     messages: [
       {
         role: "system",
-        content: "You are tasked with generating a Git commit message based on the following staged changes across multiple files. Identify only the key changes and generate a concise commit message in the format: <type>: <description>. The commit message must be a single line, in all lowercase, without a scope or body, and no full stops at the end. Use one of these types: feat, fix, refactor, docs, test, or chore. Do not mention file names unless a file was renamed or is essential to understanding the change. Focus on the most important change, and the message must not exceed 72 characters."
+        content: `You are tasked with generating a Git commit message for the following staged changes across multiple files. Strictly follow the instructions given below to generate the commit message. The instructions are given according to order of importance, as such, make sure each instruction is followed before moving on to the next. Likewise, make sure all instructions are followed successfully.
+          - Ensure the description is written in the present-tense(start with a present tense verb such as add, fix, update, remove, improve, implement, etc...) (IMPORTANT! follow this for java repositories as well).
+          - Identify the key changes only and generate a detailed but brief commit message in the format "<type>: <description>".
+          - Use one of these types: feat, fix, refactor, docs, test, or chore.
+          - The commit message must be a single line, in all lowercase, without a scope or body, and no full stops at the end.
+          - Ensure the message does not exceed 72 characters.
+          - Do not mention file names unless a file was renamed or is essential for understanding the changes.
+          - Focus on the most important changes.`
       },
       {
         role: "user",
@@ -156,7 +163,7 @@ ${diff}`
   return message.text.trim();
 }
 
-const version = "0.2.2";
+const version = "0.3.1";
 
 yargs(hideBin(process.argv)).scriptName("noto").usage("$0 [args]").command(
   "config",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@snelusha/noto",
   "type": "module",
-  "version": "0.2.3",
+  "version": "0.3.1",
   "description": "generate clean commit messages in a snap! ✨",
   "license": "MIT",
   "author": {