gityo 1.0.11 → 1.0.12

package/README.md

@@ -46,13 +46,14 @@ If you already staged files before running `gityo`, only those are used for the
 gityo
 gityo --generate
 gityo --model fast --generate
-gityo --message "fix login redirect bug"
+gityo --style concise --generate
+gityo --input "fix login redirect bug"
 gityo --yolo
 ```
 
 ## AI setup
 
-A configured model is required — gityo won't run without one, and the API key must be resolvable from your environment even when you pass `--message`. Models live in a `models` map in your config file. Each key is a name you can pick with `--model`; the `default` key is used when you don't pass `--model`:
+A configured model is required — gityo won't run without one, and the API key must be resolvable from your environment even when you pass `--input`. Models live in a `models` map in your config file. Each key is a name you can pick with `--model`; the `default` key is used when you don't pass `--model`:
 
 ```json
 {
@@ -68,7 +69,8 @@ A configured model is required — gityo won't run without one, and the API key
       "apiKeyEnv": "OPENAI_API_KEY",
       "model": "gpt-5-mini"
     }
-  }
+  },
+  "style": "concise"
 }
 ```
 
@@ -101,6 +103,7 @@ Then use:
 ```bash
 gityo --generate
 gityo --model fast --generate
+gityo --style concise --generate
 ```
 
 Providers are the official Vercel AI SDK packages: `@ai-sdk/openai`, `@ai-sdk/openai-compatible`, `@ai-sdk/anthropic`, `@ai-sdk/google`, `@ai-sdk/xai`, `@ai-sdk/azure`, `@ai-sdk/amazon-bedrock`, `@ai-sdk/groq`, `@ai-sdk/mistral`, `@ai-sdk/deepseek`, `@ai-sdk/togetherai`, `@ai-sdk/fireworks`, `@ai-sdk/perplexity`, `@ai-sdk/cohere`, `@ai-sdk/cerebras`, `@ai-sdk/luma`, `@ai-sdk/fal`, `@ai-sdk/deepinfra`, `@ai-sdk/google-vertex`, `@openrouter/ai-sdk-provider`, plus `ai-sdk-ollama`, `ollama-ai-provider-v2`, `workers-ai-provider`, `zhipu-ai-provider`, `sambanova-ai-provider`, `vercel-minimax-ai-provider`, `@aihubmix/ai-sdk-provider`, `ai-gateway-provider`, `@friendliai/ai-provider`, `@helicone/ai-sdk-provider`, and `ai-sdk-provider-opencode-sdk`.
@@ -116,7 +119,7 @@ gityo config
 Config is edited by hand in a JSON file. Project config goes in:
 
 ```text
-.gityo.config.json
+.gityo.json
 ```
 
 Global config goes in:
@@ -151,6 +154,13 @@ Example:
       "model": "gpt-5-nano"
     }
   },
+  "style": "concise",
+  "styles": {
+    "team": "Use conventional commits. Keep the subject under 72 characters.",
+    "release": {
+      "path": ".gityo/release-style.md"
+    }
+  },
   "autoAcceptMessage": false,
   "postCommand": "push",
   "autoRunPostCommand": false,
@@ -160,6 +170,35 @@ Example:
 }
 ```
 
+### Commit message styles
+
+Styles control the base commit-message convention sent to the model. Built-in
+styles are `default`, `concise`, `explanatory`, `plain`, and `gitmoji`.
+
+- `default` uses conventional commits and adds a body only for substantial,
+  multi-part changes that benefit from more context.
+- `concise` uses conventional commits and adds a body only when it is essential.
+- `explanatory` uses conventional commits and encourages a useful explanatory
+  body.
+- `plain` produces a short, non-conventional imperative subject line.
+- `gitmoji` prefixes a conventional subject with a relevant gitmoji.
+
+Choose a default with `style`, or select one for a command with `--style`:
+
+```bash
+gityo --style team --generate
+```
+
+Custom `styles` extend the built-ins. A custom style with the same name replaces
+the built-in style. A style can be inline text or an object with a `path` to a
+prompt file. File paths are passed to Node's `path.resolve()`, so relative paths
+resolve from the directory where you run `gityo`.
+
+Style selection priority is `--style`, then config `style`, then `default`.
+
+`instructions` uses the same format. Set it to a string or `{ "path": "..." }`
+to load additional instructions from a file.
+
 ### Large changes
 
 When the diff is small, it is sent to the model as-is. When it is too large for one request, gityo minimizes it first:
@@ -186,5 +225,5 @@ Keep the subject line under 72 characters.
 Priority is simple:
 
 - `.gityo.md` for repo-specific instructions
-- `.gityo.config.json` for project config
+- `.gityo.json` for project config
 - `~/.config/gityo.json` for your defaults

package/dist/index.js

@@ -1710,7 +1710,7 @@ function useColor() {
 	if (process$1.env.FORCE_COLOR || process$1.env.CLICOLOR_FORCE !== void 0) return true;
 }
 new Command();
-var version$4 = "1.0.11";
+var version$4 = "1.0.12";
 Object.freeze({ status: "aborted" });
 function $constructor$3(name$16, initializer$6, params) {
 	function init$1(inst, def) {
@@ -175933,29 +175933,34 @@ const modelSchema = object$4({
 	apiUrl: url$3().optional(),
 	options: record$3(string$6(), unknown$3()).optional()
 });
+const instructionSchema = union$4([string$6().min(1), object$4({ path: string$6().min(1) })]);
 const configSchema = object$4({
 	$schema: url$3(),
 	models: record$3(string$6().min(1), modelSchema),
-	autoAcceptMessage: boolean$5(),
-	instructions: string$6().min(1),
+	instructions: instructionSchema,
+	style: string$6().min(1),
+	styles: record$3(string$6().min(1), instructionSchema),
 	maxDiffTokens: number$5().int().min(1e3),
 	perFileCap: number$5().int().min(50),
-	postCommand: _enum$4(["push", "push-and-pull"]).nullable(),
-	autoRunPostCommand: boolean$5()
+	autoAcceptMessage: boolean$5(),
+	autoRunPostCommand: boolean$5(),
+	postCommand: _enum$4(["push", "push-and-pull"]).nullable()
 }).partial();
 function resolveConfig(input) {
 	const parsed = configSchema.parse(input);
 	return {
 		models: parsed.models,
+		style: parsed.style,
+		styles: parsed.styles,
 		instructions: parsed.instructions,
-		autoAcceptCommitMessage: parsed.autoAcceptMessage ?? false,
 		maxDiffTokens: parsed.maxDiffTokens,
 		perFileCap: parsed.perFileCap,
-		postCommand: parsed.postCommand === void 0 ? "push" : parsed.postCommand,
-		autoRunPostCommand: parsed.autoRunPostCommand ?? false
+		autoAcceptCommitMessage: parsed.autoAcceptMessage ?? false,
+		autoRunPostCommand: parsed.autoRunPostCommand ?? false,
+		postCommand: parsed.postCommand === void 0 ? "push" : parsed.postCommand
 	};
 }
-const PROJECT_CONFIG_FILE_NAME = ".gityo.config.json";
+const PROJECT_CONFIG_FILE_NAME = ".gityo.json";
 const GLOBAL_CONFIG_FILE_PATH = path.join(os.homedir(), ".config", "gityo.json");
 async function loadConfig(cwd = process.cwd()) {
 	const [globalConfig$3, projectConfig, projectInstructions] = await Promise.all([
@@ -181257,7 +181262,6 @@ function hardSplit(text$1, maxTokens) {
 	if (current.length > 0) chunks.push(current);
 	return chunks;
 }
-var system_prompt_default = "You are a strict Git commit message generator. ONLY output the commit message, nothing else.\n\nREQUIRED FORMAT:\n- First line: <type>(<scope>): <subject> (max 50 characters)\n- Types: feat, fix, docs, style, refactor, perf, test, chore, ci\n- Subject: imperative mood, lowercase, no period\n- If body needed: blank line + detailed explanation (wrapped at 72 chars)\n\nSTRICT RULES:\n1. MUST use conventional commits format: type(scope): subject\n2. Subject line MUST be under 50 characters\n3. Subject MUST be in imperative mood (e.g., \"add\", \"fix\", \"update\")\n4. Subject MUST be lowercase\n5. Subject MUST NOT end with a period\n6. MUST provide clear context about WHAT changed and WHY\n7. MUST be specific about affected functions, components, or modules\n8. MUST NOT use vague terms like \"Update\", \"Fix stuff\", \"Changes\"\n9. If including a body, MUST have exactly one blank line between subject and body\n10. Body lines MUST wrap at 72 characters\n\nOUTPUT INSTRUCTION:\nReturn ONLY the commit message. No explanations, no extra text, no markdown formatting.\n\nEXAMPLE:\nfeat(llm): add support for streaming responses\n\nImplement streaming response handling for commit message\ngeneration to improve user experience with large diffs.\nAdds new stream event handlers and updates the API contract.\n\nAnalyze the diff and generate a message following ALL rules above.";
 const summarizePrompt = `You summarize parts of a large git diff for a commit message generator.
 Describe WHAT changed, in which files or modules, and any observable intent.
 Be factual and terse. Do NOT write a commit message. Maximum 120 words.`;
@@ -181268,8 +181272,8 @@ async function ask(languageModel, system, messages) {
 		messages
 	})).text.trim();
 }
-async function generateCommitMessage(languageModel, instructions, diff) {
-	return ask(languageModel, system_prompt_default, [{
+async function generateCommitMessage(languageModel, style, instructions, diff) {
+	return ask(languageModel, style, [{
 		role: "user",
 		content: `Changes:\n${diff}`
 	}, {
@@ -181286,8 +181290,8 @@ async function summarizeChanges(languageModel, toc, chunk$1) {
 		content: "Summarize these changes."
 	}]);
 }
-async function generateCommitMessageFromSummaries(languageModel, instructions, toc, summaries) {
-	return ask(languageModel, system_prompt_default, [{
+async function generateCommitMessageFromSummaries(llm, style, instructions, toc, summaries) {
+	return ask(llm, style, [{
 		role: "user",
 		content: `All changed files:\n${toc}\n\nSummaries of all changes:\n${summaries.map((summary, index$2) => `Part ${index$2 + 1}:\n${summary}`).join("\n\n")}`
 	}, {
@@ -181315,6 +181319,28 @@ function resolveLanguageModel(modelConfig) {
 		...modelConfig.options
 	}).languageModel(modelConfig.model);
 }
+const BUILTIN_STYLES = {
+	default: "You are a strict Git commit message generator. ONLY output the commit message, nothing else.\n\nREQUIRED FORMAT:\n\n- First line: <type>(<scope>): <subject> (max 50 characters)\n- Types: feat, fix, docs, style, refactor, perf, test, chore, ci\n- Subject: imperative mood, lowercase, no period\n- Optional body: blank line + concise explanation (wrapped at 72 chars)\n\nSTRICT RULES:\n\n- MUST use conventional commits format: type(scope): subject\n- Subject line MUST be under 50 characters\n- Subject MUST be in imperative mood (e.g., \"add\", \"fix\", \"update\")\n- Subject MUST be lowercase\n- Subject MUST NOT end with a period\n- MUST provide clear context about WHAT changed\n- MUST be specific about affected functions, components, or modules\n- MUST NOT use vague terms like \"Update\", \"Fix stuff\", \"Changes\"\n- Do NOT include a body for a small or focused change\n- Include a body only when the diff contains several substantial related changes and explaining them adds useful context\n- When a body is warranted, explain WHY when the rationale or impact is not obvious; do not force or invent a reason\n- If including a body, MUST have exactly one blank line between subject and body\n- Body lines MUST wrap at 72 characters\n\nOUTPUT INSTRUCTION:\nReturn ONLY the commit message. No explanations, no extra text, no markdown formatting.\n\nEXAMPLE:\nfeat(llm): add streaming responses\n\nAnalyze the diff and generate a message following ALL rules above.\n",
+	concise: "You are a strict Git commit message generator. ONLY output the commit message, nothing else.\n\nREQUIRED FORMAT:\n- First line: <type>(<scope>): <subject> (max 50 characters)\n- Types: feat, fix, docs, style, refactor, perf, test, chore, ci\n- Subject: imperative mood, lowercase, no period\n- Exceptional body: blank line + minimal explanation (wrapped at 72 chars)\n\nSTRICT RULES:\n- MUST use conventional commits format: type(scope): subject\n- Subject line MUST be under 50 characters\n- Subject MUST be in imperative mood (e.g., \"add\", \"fix\", \"update\")\n- Subject MUST be lowercase\n- Subject MUST NOT end with a period\n- MUST provide clear context about the most important change\n- MUST be specific about affected functions, components, or modules\n- MUST NOT use vague terms like \"Update\", \"Fix stuff\", \"Changes\"\n- MUST prefer a subject line with no body\n- Include a body only when absolutely necessary to communicate critical context that cannot be expressed in the subject\n- If including a body, keep it as short as possible and explain WHY only when that rationale or impact is essential and supported by the diff\n- If including a body, MUST have exactly one blank line between subject and body\n- Body lines MUST wrap at 72 characters\n\nOUTPUT INSTRUCTION:\nReturn ONLY the commit message. No explanations, no extra text, no markdown formatting.\n\nEXAMPLE:\nfix(config): preserve provider settings\n\nAnalyze the diff and generate a message following ALL rules above.\n",
+	explanatory: "You are a strict Git commit message generator. ONLY output the commit message, nothing else.\n\nREQUIRED FORMAT:\n- First line: <type>(<scope>): <subject> (max 72 characters)\n- Types: feat, fix, docs, style, refactor, perf, test, chore, ci\n- Subject: imperative mood, lowercase, no period\n- Encouraged body: blank line + concise explanation (wrapped at 72 chars)\n\nSTRICT RULES:\n- MUST use conventional commits format: type(scope): subject\n- Subject line MUST be under 72 characters\n- Subject MUST be in imperative mood (e.g., \"add\", \"fix\", \"update\")\n- Subject MUST be lowercase\n- Subject MUST NOT end with a period\n- MUST provide clear context about WHAT changed\n- MUST be specific about affected functions, components, or modules\n- MUST NOT use vague terms like \"Update\", \"Fix stuff\", \"Changes\"\n- Include a body whenever it adds meaningful context beyond the subject\n- Use the body to explain WHY the change was made or its impact when supported by the diff; do not force or invent a reason\n- Omit the body only when it would merely repeat the subject\n- If including a body, MUST have exactly one blank line between subject and body\n- Body lines MUST wrap at 72 characters\n\nOUTPUT INSTRUCTION:\nReturn ONLY the commit message. No explanations, no extra text, no markdown formatting.\n\nEXAMPLE:\nfix(config): preserve custom provider settings\n\nReload stored provider options before applying command-line overrides to\nprevent unrelated settings from being discarded.\n\nAnalyze the diff and generate a message following ALL rules above.\n",
+	plain: "You are a strict Git commit message generator. ONLY output the commit message, nothing else.\n\nREQUIRED FORMAT:\n- Only line: <subject> (max 72 characters)\n- Subject: imperative mood, lowercase, no punctuation\n- No prefix, scope, emoji, or body\n\nSTRICT RULES:\n- MUST output exactly one plain subject line\n- Complete line MUST be under 72 characters\n- Subject MUST start with an imperative verb (e.g., \"add\", \"fix\", \"update\")\n- Subject MUST be lowercase\n- Subject MUST NOT end with punctuation\n- MUST provide clear context about the most important change\n- MUST be specific about affected functions, components, or modules\n- MUST NOT use vague terms like \"Update\", \"Fix stuff\", \"Changes\"\n- MUST NOT use conventional commit types, scopes, prefixes, or emoji\n- MUST NOT include a body\n\nOUTPUT INSTRUCTION:\nReturn ONLY the commit message. No explanations, no extra text, no markdown formatting.\n\nEXAMPLE:\npreserve custom provider settings\n\nAnalyze the diff and generate a message following ALL rules above.\n",
+	gitmoji: "You are a strict Git commit message generator. ONLY output the commit message, nothing else.\n\nREQUIRED FORMAT:\n- Only line: <gitmoji> <type>(<scope>): <subject> (max 72 characters)\n- Types: feat, fix, docs, style, refactor, perf, test, chore, ci\n- Subject: imperative mood, lowercase, no period\n- No body\n\nSTRICT RULES:\n- MUST use gitmoji conventional commits format: <gitmoji> type(scope): subject\n- MUST choose exactly one gitmoji that best represents the change\n- Use relevant gitmoji such as ✨ for features, 🐛 for fixes, 📝 for documentation, ♻️ for refactoring, ✅ for tests, or 🔧 for configuration\n- Complete line MUST be under 72 characters\n- Subject MUST be in imperative mood (e.g., \"add\", \"fix\", \"update\")\n- Subject MUST be lowercase\n- Subject MUST NOT end with a period\n- MUST provide clear context about the most important change\n- MUST be specific about affected functions, components, or modules\n- MUST NOT use vague terms like \"Update\", \"Fix stuff\", \"Changes\"\n- MUST NOT include a body\n\nOUTPUT INSTRUCTION:\nReturn ONLY the commit message. No explanations, no extra text, no markdown formatting.\n\nEXAMPLE:\n✨ feat(cli): add interactive style selection\n\nAnalyze the diff and generate a message following ALL rules above.\n"
+};
+function getStyleKeys(styles$2) {
+	return Object.keys({
+		...BUILTIN_STYLES,
+		...styles$2
+	});
+}
+async function resolveStyle(styleKey, styles$2) {
+	const style = styles$2?.[styleKey] ?? BUILTIN_STYLES[styleKey];
+	if (!style) return;
+	return resolveInstructionContent(style);
+}
+async function resolveInstructionContent(instruction) {
+	if (typeof instruction === "string") return instruction;
+	return readFile(path.resolve(instruction.path), "utf8");
+}
 const isUpKey = (key$1, keybindings = []) => key$1.name === "up" || keybindings.includes("vim") && key$1.name === "k" || keybindings.includes("emacs") && key$1.ctrl && key$1.name === "p";
 const isDownKey = (key$1, keybindings = []) => key$1.name === "down" || keybindings.includes("vim") && key$1.name === "j" || keybindings.includes("emacs") && key$1.ctrl && key$1.name === "n";
 const isSpaceKey = (key$1) => key$1.name === "space";
@@ -198117,7 +198143,11 @@ async function runWithLoading(label, task) {
 	let index$2 = 0;
 	const interval = setInterval(() => {
 		readline.cursorTo(process.stdout, 0);
-		process.stdout.write(`${source_default.cyan(frames[index$2])} ${source_default.cyan(label)} ${source_default.reset.dim("...")}`);
+		process.stdout.write([
+			source_default.cyan(frames[index$2]) + " ",
+			source_default.cyan(label),
+			source_default.reset.dim("...")
+		].join(""));
 		index$2 = (index$2 + 1) % frames.length;
 	}, 80);
 	try {
@@ -198143,10 +198173,17 @@ async function mainController(options = {}) {
 		throw new Error(hint);
 	}
 	const languageModel = resolveLanguageModel(modelConfig);
+	const styleKey = options.style ?? config$4.style ?? "default";
+	const style = await resolveStyle(styleKey, config$4.styles);
+	if (!style) {
+		const availableStyles = getStyleKeys(config$4.styles).join(", ");
+		throw new Error(`Style '${styleKey}' is not configured. Available styles: ${availableStyles}.`);
+	}
+	const instructions = config$4.instructions ? await resolveInstructionContent(config$4.instructions) : null;
 	const forceLLMGenerate = options.generate || options.yolo;
 	const forceExecPostCommand = options.post || options.yolo;
-	let finalCommitMessage = options.message?.trim() ?? "";
-	if (typeof options.message === "string" && finalCommitMessage.length === 0) throw new Error("Provided commit message cannot be empty.");
+	let finalCommitMessage = options.input?.trim() ?? "";
+	if (typeof options.input === "string" && finalCommitMessage.length === 0) throw new Error("Provided commit message input cannot be empty.");
 	const files = await getChangedFiles(git);
 	if (files.length === 0) return console.log("No changed files found.");
 	const { diff, hasStaged } = await getCommitDiff(git);
@@ -198168,11 +198205,12 @@ async function mainController(options = {}) {
 		finalCommitMessage = (await runWithLoading("Generating commit message", () => generateMessage({
 			git,
 			languageModel,
-			instructions: config$4.instructions ?? null,
+			style,
+			instructions,
 			diff,
 			files,
-			maxDiffTokens: config$4.maxDiffTokens ?? DEFAULT_MAX_DIFF_TOKENS,
-			perFileCap: config$4.perFileCap ?? DEFAULT_PER_FILE_CAP
+			perFileCap: config$4.perFileCap ?? DEFAULT_PER_FILE_CAP,
+			maxDiffTokens: config$4.maxDiffTokens ?? DEFAULT_MAX_DIFF_TOKENS
 		}))).trim();
 		if (finalCommitMessage.length === 0) throw new Error("The selected model returned an empty commit message.");
 		console.log(source_default.cyan.dim(finalCommitMessage));
@@ -198194,15 +198232,13 @@ async function mainController(options = {}) {
 	if (config$4.postCommand === "push-and-pull") await liveGit.pull();
 }
 async function generateMessage(options) {
-	const { git, languageModel, instructions, diff } = options;
-	if (estimateTokens(diff) <= options.maxDiffTokens) return generateCommitMessage(languageModel, instructions, diff);
-	console.log(source_default.yellow("• Large diff detected, minimizing"));
+	const { git, languageModel, style, instructions, diff } = options;
+	if (estimateTokens(diff) <= options.maxDiffTokens) return generateCommitMessage(languageModel, style, instructions, diff);
 	const { toc, body } = await minimizeDiff(git, {
 		perFileCap: options.perFileCap,
 		allFiles: options.files
 	});
-	if (estimateTokens(toc) + estimateTokens(body) <= options.maxDiffTokens) return generateCommitMessage(languageModel, instructions, `${toc}\n\n${body}`);
-	console.log(source_default.yellow("• Diff still too large, summarizing in parts"));
+	if (estimateTokens(toc) + estimateTokens(body) <= options.maxDiffTokens) return generateCommitMessage(languageModel, style, instructions, `${toc}\n\n${body}`);
 	let effectiveToc = toc;
 	let chunkBudget = options.maxDiffTokens - estimateTokens(effectiveToc) - PROMPT_RESERVE_TOKENS;
 	if (chunkBudget < MIN_CHUNK_BUDGET_TOKENS) {
@@ -198219,7 +198255,7 @@ async function generateMessage(options) {
 		}
 	}
 	await Promise.all(Array.from({ length: Math.min(MAP_CONCURRENCY, chunks.length) }, worker));
-	return generateCommitMessageFromSummaries(languageModel, instructions, effectiveToc, summaries);
+	return generateCommitMessageFromSummaries(languageModel, style, instructions, effectiveToc, summaries);
 }
 var AppUserCanceledError = class extends Error {};
 function handleError(fn$1) {
@@ -198231,9 +198267,9 @@ function handleError(fn$1) {
 		}
 	});
 }
-const app = new Command().name("gityo").version(`v${version$4}`, "-v, --version", "Show the current version.").description("Stage changes, generate or enter a commit message, create a commit, and run a post-commit git command.").option("-g, --generate", "Generate a commit message and commit without asking.").option("-m, --message <message>", "Use the provided message as the commit message.").option("-p, --post", "Run the post-commit git command without asking.").option("--model <model>", "Model key from config to use (defaults to \"default\").").option("-y, --yolo", "Skip all questions, and generate message, commit, run post command. [Will fail if no model available]").action((options) => {
-	if (options.generate && options.message) {
-		console.error("Cannot use --generate and --message together.");
+const app = new Command().name("gityo").description("Stage changes, generate or enter a commit message, create a commit, and run a post-commit git command.").option("-i, --input <input>", "Use the provided input as the commit message.").option("-s, --style <style>", "Commit message style key to use (defaults to \"default\").").option("-m, --model <model>", "Model key from config to use (defaults to \"default\").").option("-g, --generate", "Generate a commit message and commit without asking.").option("-p, --post", "Run the post-commit git command without asking.").option("-y, --yolo", "Skip all questions, and generate message, commit, run post command. [Will fail if no model available]").version(`v${version$4}`, "-v, --version", "Show the current version.").action((options) => {
+	if (options.generate && options.input) {
+		console.error("Cannot use --generate and --input together.");
 		process.exit(1);
 	}
 	handleError(() => mainController(options));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gityo",
-  "version": "1.0.11",
+  "version": "1.0.12",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/NazmusSayad/gityo.git"
@@ -8,12 +8,13 @@
   "sideEffects": false,
   "type": "module",
   "scripts": {
-    "lint": "tsc --noEmit && eslint .",
-    "fix": "tsc --noEmit && eslint . --fix",
-    "start": "tsx --watch ./src/index.ts",
+    "typecheck": "tsc --noEmit",
+    "typecheck:watch": "tsc --noEmit --watch",
+    "lint": "eslint .",
+    "lint:fix": "eslint . --fix",
     "build": "tsdown --config ./tsdown.config.ts",
-    "dev": "concurrently --names \"R,T\" --prefix-colors \"blue.dim,magenta.dim\" \"tsdown --config ./tsdown.config.ts --watch\" \"tsc --noEmit --watch\"",
-    "dev:tsc": "tsc --noEmit --watch",
+    "dev": "tsdown --config ./tsdown.config.ts --watch",
+    "start": "node --watch ./dist/index.js",
     "json": "tsx ./src/json.ts"
   },
   "bin": {