feat: add extensible recipe registry and CLI command by Akash-nath29 · Pull Request #125 · Akash-nath29/Coderrr

Akash-nath29 · 2026-01-30T20:30:48Z

This pull request introduces a new "Recipe System" to Coderrr, allowing users to manage and execute pre-defined sets of tasks (recipes). The implementation includes recipe storage, listing, validation, and documentation, as well as initial testing to ensure the system works as intended.

Recipe System Implementation:

Added RecipeManager class in src/recipeManager.js for managing recipes, including directory setup, listing, and retrieval of recipes. It also creates a default "ping" recipe if none exist.
Added a recipe validator utility in src/utils/recipeValidator.js to ensure custom recipes have the required structure (name and a non-empty tasks array).

User Interface and Documentation:

Added src/recipeUI.js to display available recipes in a user-friendly, colorized format.
Added a new documentation section in docs/recipes.md explaining how to use and create recipes in Coderrr.

Testing:

Added a test in test/recipes.test.js to verify that the default "ping" recipe is present and correctly structured.

feat: add Coderrr Insights dashboard for productivity tracking and Skills for better workflow

feat: add extensible recipe registry and CLI command

vercel · 2026-01-30T20:30:54Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
coderrr-backend	Ready	Preview, Comment	Jan 30, 2026 8:30pm

github-actions · 2026-01-30T20:31:01Z

🚀 Thanks for opening a Pull Request!

A maintainer will review this soon.

Meanwhile:
✔ Ensure tests are passing
✔ Link related issues
✔ Code follows the project guidelines

Your contribution helps make this project better!

Copilot

Pull request overview

This PR introduces a first version of a “recipe system” that discovers JSON recipes from a user directory, exposes them via a new coderrr recipe CLI command, and documents how to create and list recipes, along with an initial test.

Changes:

Added RecipeManager to manage recipes under ~/.coderrr/recipes, including creating a default ping recipe, listing recipes, and loading a single recipe.
Added recipeUI and a new coderrr recipe CLI command for listing and (eventually) running recipes, plus a recipeValidator utility and a Jest test to verify the default recipe.
Added docs/recipes.md to explain recipe usage and how to define custom recipes.

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
`src/recipeManager.js`	Implements recipe storage in `~/.coderrr/recipes`, ensures the directory exists, seeds a default `ping` recipe, and provides listing and lookup helpers used by the CLI and tests.
`src/recipeUI.js`	Adds a small chalk-based UI helper to pretty-print the available recipes read from `RecipeManager`.
`src/utils/recipeValidator.js`	Introduces a utility for validating recipe objects (name and non-empty tasks), intended for use when loading custom recipes.
`bin/coderrr.js`	Wires in the new recipe system through a `recipe` subcommand (with list and run modes) and keeps the existing `insights` command, extending the CLI surface area for recipes.
`docs/recipes.md`	Documents the recipe concept, CLI usage (`coderrr recipe --list` / `coderrr recipe <name>`), and shows a JSON example for defining a custom recipe file.
`test/recipes.test.js`	Adds a Jest test that exercises `RecipeManager.listRecipes()` and asserts that the default `ping` recipe is present and correctly named.

Copilot · 2026-01-30T20:35:29Z

src/recipeManager.js

+    ensureDirectory() {
+        if (!fs.existsSync(RECIPES_DIR)) {
+            fs.mkdirSync(RECIPES_DIR, { recursive: true });
+            // Add a default "Hello World" recipe


The comment says this creates a default "Hello World" recipe, but the actual recipe is named "ping" and has a different description. Please update the comment to match the behavior so future readers are not misled.

Suggested change

// Add a default "Hello World" recipe

// Add a default "ping" health check recipe

Copilot · 2026-01-30T20:35:30Z

src/recipeManager.js

+        return files.map(f => {
+            const content = JSON.parse(fs.readFileSync(path.join(RECIPES_DIR, f), 'utf8'));
+            return { id: f.replace('.json', ''), ...content };
+        });
+    }
+
+    getRecipe(name) {
+        const filePath = path.join(RECIPES_DIR, `${name}.json`);
+        if (fs.existsSync(filePath)) {
+            return JSON.parse(fs.readFileSync(filePath, 'utf8'));


JSON.parse is called on each recipe file without any error handling, so a single malformed or partially-written JSON file in the recipes directory will throw and break listRecipes() entirely. Consider wrapping this read/parse in a try/catch and either skipping invalid recipes or surfacing a clear validation error, potentially reusing the recipe validator utility.

Suggested change

return files.map(f => {

const content = JSON.parse(fs.readFileSync(path.join(RECIPES_DIR, f), 'utf8'));

return { id: f.replace('.json', ''), ...content };

});

}

getRecipe(name) {

const filePath = path.join(RECIPES_DIR, `${name}.json`);

if (fs.existsSync(filePath)) {

return JSON.parse(fs.readFileSync(filePath, 'utf8'));

const recipes = [];

for (const f of files) {

const filePath = path.join(RECIPES_DIR, f);

try {

const raw = fs.readFileSync(filePath, 'utf8');

const content = JSON.parse(raw);

recipes.push({ id: f.replace('.json', ''), ...content });

} catch (error) {

console.error(`Failed to read or parse recipe file "${f}": ${error.message}`);

}

}

return recipes;

}

getRecipe(name) {

const filePath = path.join(RECIPES_DIR, `${name}.json`);

if (fs.existsSync(filePath)) {

try {

const raw = fs.readFileSync(filePath, 'utf8');

return JSON.parse(raw);

} catch (error) {

throw new Error(`Failed to read or parse recipe "${name}": ${error.message}`);

}

Copilot · 2026-01-30T20:35:30Z

src/recipeManager.js

+    getRecipe(name) {
+        const filePath = path.join(RECIPES_DIR, `${name}.json`);
+        if (fs.existsSync(filePath)) {
+            return JSON.parse(fs.readFileSync(filePath, 'utf8'));


getRecipe also calls JSON.parse without guarding against invalid JSON, which means a corrupt recipe file will cause the CLI command to throw instead of returning null or a structured error. It would be safer to catch parse errors here and either return null or propagate a user-friendly error, ideally using the shared recipe validation logic.

Suggested change

return JSON.parse(fs.readFileSync(filePath, 'utf8'));

const content = fs.readFileSync(filePath, 'utf8');

try {

return JSON.parse(content);

} catch (error) {

// If the recipe file contains invalid JSON, treat it as unavailable

console.error(`Failed to parse recipe "${name}" from ${filePath}: ${error.message}`);

return null;

}

Copilot · 2026-01-30T20:35:30Z

src/utils/recipeValidator.js

+const validateRecipe = (recipe) => {
+    const errors = [];
+    if (!recipe.name) errors.push("Missing 'name' field");
+    if (!Array.isArray(recipe.tasks) || recipe.tasks.length === 0) {
+        errors.push("'tasks' must be a non-empty array");
+    }
+    return {
+        valid: errors.length === 0,
+        errors
+    };
+};
+
+module.exports = { validateRecipe };


This validateRecipe helper is not imported or used anywhere, so recipes are never actually validated before use even though the PR description says custom recipes are validated. Either wire this into RecipeManager/the CLI flow (e.g., when loading or running recipes) or remove it until it is integrated to avoid dead code and confusion.

Copilot · 2026-01-30T20:35:30Z

test/recipes.test.js

+describe('Recipe System', () => {
+    test('should find the default ping recipe', () => {
+        const recipes = recipeManager.listRecipes();
+        const ping = recipes.find(r => r.id === 'ping');
+        expect(ping).toBeDefined();
+        expect(ping.name).toBe('ping');


This test uses the real RecipeManager singleton, which writes to and reads from ~/.coderrr/recipes and assumes a default ping recipe exists. That couples test results to the developer's home directory state (e.g., if they delete or change their recipes the test will fail), so consider isolating it by mocking os.homedir/fs or allowing RecipeManager to be pointed at a temporary directory.

Copilot · 2026-01-30T20:35:31Z

docs/recipes.md

+```json
+{
+  "name": "Quick Express",
+  "tasks": ["Initialize npm", "Install express", "Create app.js"]
+}


The JSON example code block is not closed with a matching fence, which will cause the Markdown renderer to treat the rest of the document as part of the code block. Please add a closing ``` line after the JSON snippet so the usage text renders correctly.

Dbansal06 and others added 5 commits January 30, 2026 23:49

feat: add extensible recipe registry and CLI command

225d83e

Merge pull request #124 from Akash-nath29/dev

3c45703

feat: add Coderrr Insights dashboard for productivity tracking and Skills for better workflow

Merge branch 'main' into feature/recipe-system

6460639

Merge pull request #120 from Dbansal06/feature/recipe-system

e3dd274

feat: add extensible recipe registry and CLI command

Fix issue @coderrr.js

dbc3297

Copilot AI review requested due to automatic review settings January 30, 2026 20:30

Copilot started reviewing on behalf of Akash-nath29 January 30, 2026 20:31 View session

Copilot AI reviewed Jan 30, 2026

View reviewed changes

Akash-nath29 merged commit eac657d into dev Jan 30, 2026
36 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: add extensible recipe registry and CLI command#125

feat: add extensible recipe registry and CLI command#125
Akash-nath29 merged 5 commits intodevfrom
feature

Akash-nath29 commented Jan 30, 2026

Uh oh!

vercel bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Jan 30, 2026

Uh oh!

Copilot AI Jan 30, 2026

Uh oh!

Copilot AI Jan 30, 2026

Uh oh!

Copilot AI Jan 30, 2026

Uh oh!

Copilot AI Jan 30, 2026

Uh oh!

Copilot AI Jan 30, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	// Add a default "Hello World" recipe
	// Add a default "ping" health check recipe

-        return files.map(f => {
-            const content = JSON.parse(fs.readFileSync(path.join(RECIPES_DIR, f), 'utf8'));
-            return { id: f.replace('.json', ''), ...content };
-        });
-    }
-    getRecipe(name) {
-        const filePath = path.join(RECIPES_DIR, `${name}.json`);
-        if (fs.existsSync(filePath)) {
-            return JSON.parse(fs.readFileSync(filePath, 'utf8'));
+        const recipes = [];
+        for (const f of files) {
+            const filePath = path.join(RECIPES_DIR, f);
+            try {
+                const raw = fs.readFileSync(filePath, 'utf8');
+                const content = JSON.parse(raw);
+                recipes.push({ id: f.replace('.json', ''), ...content });
+            } catch (error) {
+                console.error(`Failed to read or parse recipe file "${f}": ${error.message}`);
+            }
+        }
+        return recipes;
+    }
+    getRecipe(name) {
+        const filePath = path.join(RECIPES_DIR, `${name}.json`);
+        if (fs.existsSync(filePath)) {
+            try {
+                const raw = fs.readFileSync(filePath, 'utf8');
+                return JSON.parse(raw);
+            } catch (error) {
+                throw new Error(`Failed to read or parse recipe "${name}": ${error.message}`);
+            }

-            return JSON.parse(fs.readFileSync(filePath, 'utf8'));
+            const content = fs.readFileSync(filePath, 'utf8');
+            try {
+                return JSON.parse(content);
+            } catch (error) {
+                // If the recipe file contains invalid JSON, treat it as unavailable
+                console.error(`Failed to parse recipe "${name}" from ${filePath}: ${error.message}`);
+                return null;
+            }

Uh oh!

Conversation

Akash-nath29 commented Jan 30, 2026

Uh oh!

vercel bot commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants