feat: add ai command for cli to start the project #7352

denar90 · 2025-06-16T11:45:19Z

🎉 Thanks for submitting a pull request! 🎉

Summary

Fixes #<replace_with_issue_number>

For us to review and ship your PR efficiently, please perform the following steps:

Open a bug/issue before writing your code 🧑‍💻. This ensures we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or something that`s on fire 🔥 (e.g. incident related), you can skip this step.
Read the contribution guidelines 📖. This ensures your code follows our style guide and
passes our tests.
Update or add tests (if any source code was changed or added) 🧪
Update or add documentation (if features were changed or added) 📝
Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

github-actions · 2025-06-16T11:46:17Z

📊 Benchmark results

Comparing with 1348a3e

Dependency count: 1,081 (no change)
Package size: 288 MB ⬇️ 0.00% decrease vs. 1348a3e
Number of ts-expect-error directives: 399 (no change)

denar90 · 2025-06-23T08:51:03Z

src/commands/init/ai-rules.ts

@@ -0,0 +1,447 @@
+import { resolve } from 'node:path'


part of code here is duplication, but we still not setelled the command and want to see how it feels so then we can extract stuff into common utils after we work on making command fully public

I'm not sure why trialing the new command should mean more code duplication? If you move the generic methods you're reusing to a separate file (which I would argue should already be the case), you're making it easier for this PR to be reviewed, you're going to have less code to maintain, and you reduce the number of places where you might need to adjust things if an issue or an improvement come up.

If you then decide that you want to keep the new command in its current shape, great — you already have the code in the structure you want and no further changes are needed; if you decide you want to bin it, you can just delete it and the code you abstracted away into a separate file still makes sense on its own.

denar90 · 2025-06-23T08:51:32Z

src/commands/init/ai-rules.ts

+
+    // Step 4: Save AI instructions to file
+    if (projectInfo.prompt) {
+      const ntlContext = await fetch(


in future we don't wanna fetch context if we installing MCP

eduardoboucas · 2025-06-23T09:04:48Z

src/commands/init/ai-rules.ts

@@ -0,0 +1,447 @@
+import { resolve } from 'node:path'


I'm not sure why trialing the new command should mean more code duplication? If you move the generic methods you're reusing to a separate file (which I would argue should already be the case), you're making it easier for this PR to be reviewed, you're going to have less code to maintain, and you reduce the number of places where you might need to adjust things if an issue or an improvement come up.

If you then decide that you want to keep the new command in its current shape, great — you already have the code in the structure you want and no further changes are needed; if you decide you want to bin it, you can just delete it and the code you abstracted away into a separate file still makes sense on its own.

eduardoboucas · 2025-06-23T09:06:33Z

src/commands/init/ai-rules.ts

+}
+
+// Generate MCP configuration for the detected IDE
+const generateMcpConfig = (ide: ConsumerConfig): string => {


Why are you returning the config as a string here only to then re-parse it into an object in configureMcpForVSCode?

eduardoboucas · 2025-06-23T09:07:52Z

src/commands/init/ai-rules.ts

+    await fs.writeFile(configPath, JSON.stringify(updatedConfig, null, 2), 'utf-8')
+    log(`${chalk.green('✅')} VS Code MCP configuration saved to ${chalk.cyan('.vscode/mcp.json')}`)
+  } catch (error) {
+    throw new Error(`Failed to configure VS Code MCP: ${error instanceof Error ? error.message : 'Unknown error'}`)


When will error not be an instance of Error?

it's always unknown, but here yeah it will be Error, it's more following code pattern across repo

I see a couple of instances of that, which doesn't feel like enough of a reason to perpetuate this and just duplicate this code every time we handle an error, especially when we know for a fact that the type will be Error.

This is a normal idiom--TypeScript can't guarantee caught values are errors.

eduardoboucas · 2025-06-23T09:08:19Z

src/commands/init/ai-rules.ts

+
+// VS Code specific MCP configuration
+const configureMcpForVSCode = async (config: string, projectPath: string): Promise<void> => {
+  const configPath = resolve(projectPath, '.vscode', 'mcp.json')


nit: Save the path to the .vscode directory in a variable to avoid resolving the path multiple times.

eduardoboucas · 2025-06-23T09:09:09Z

src/commands/init/ai-rules.ts

+
+// Windsurf specific MCP configuration
+const configureMcpForWindsurf = async (config: string, _projectPath: string): Promise<void> => {
+  const { homedir } = await import('node:os')


Why are you using a dynamic import here?

eduardoboucas · 2025-06-23T09:16:39Z

src/commands/init/ai-rules.ts

+  const { api } = command.netlify
+
+  log(`${chalk.blue('🤖 Initializing AI project')} with rules...`)
+  log(`${chalk.gray('Hash:')} ${hash}`)


Do we have to print the hash? Why do people care?

src/commands/init/ai-rules.ts

eduardoboucas · 2025-06-23T09:19:01Z

src/commands/init/ai-rules.ts

+    let mcpConfigured = false
+
+    if (detectedIDE) {
+      log(`${chalk.green('✅')} Detected IDE: ${chalk.cyan(detectedIDE.presentedName)}`)


Can we settle on either "development environment" or "IDE"? Using both next to each other feels unnecessarily confusing.

eduardoboucas · 2025-06-23T09:19:40Z

src/commands/init/ai-rules.ts

+      } else {
+        log(chalk.yellowBright(`🔧 Step 2: Manual MCP Configuration`))
+        log(`   ${chalk.cyan(detectedIDE.key)} detected - MCP setup was skipped`)
+        log(`   ${chalk.gray('You can configure MCP manually later for enhanced AI capabilities')}`)


Co-authored-by: Eduardo Bouças <[email protected]>

eduardoboucas

Approving so you can get unblocked, but I left some notes and questions that I think we should be addressed.

eduardoboucas · 2025-06-23T12:46:26Z

src/commands/init/ai-rules.ts

+    log(`${chalk.green('✅')} AI instructions saved to ${chalk.cyan('AI-instructions.md')}`)
+  } catch (error) {
+    const errorMessage = error instanceof Error ? error.message : 'Unknown error'
+    log(`${chalk.yellow('⚠️')} Warning: Failed to save AI instructions: ${errorMessage}`)


The CLI has a warn method precisely for this purpose:

cli/src/utils/command-helpers.ts

Lines 185 to 188 in f449ad8

export const warn = (message = '') => {

const bang = chalk.yellow(BANG)

log(` ${bang} Warning: ${message}`)

}

eduardoboucas · 2025-06-23T12:49:10Z

src/utils/mcp-utils.ts

+ * Generate MCP configuration for the detected IDE or development environment
+ */
+export const generateMcpConfig = (ide: ConsumerConfig): Record<string, unknown> => {
+  const configs: Record<string, Record<string, unknown>> = {


It would be great to properly type this.

eduardoboucas · 2025-06-23T12:53:09Z

src/commands/init/ai-rules.ts

+  }
+}
+
+const fetchProjectInfo = async (url: string): Promise<ProjectInfo> => {


It would be great to have a comment explaining what is the URL we're hitting — is it the Netlify API, something else?

eduardoboucas · 2025-06-23T12:54:18Z

src/commands/init/ai-rules.ts

+
+const getRepoUrlFromProjectId = async (api: NetlifyAPI, projectId: string): Promise<string> => {
+  try {
+    const siteInfo = (await api.getSite({ siteId: projectId })) as SiteInfo


Do we not already have the site information populated by the base command? Or is this a different site? If we could use that, we'd avoid making an extra API call.

eduardoboucas · 2025-06-23T12:56:53Z

src/commands/init/ai-rules.ts

+        {
+          method: 'GET',
+          headers: {
+            'Content-Type': 'text/plain',


Why are you setting Content-Type on a GET request? Did you mean to use Accept?

eduardoboucas · 2025-06-23T12:58:32Z

src/commands/init/ai-rules.ts

+    }
+
+    // Update working directory to cloned repo
+    process.chdir(targetDir)


What is the purpose of this?

denar90 · 2025-06-23T13:36:11Z

Awesome 🙌 thank you

…5-add-ai-command-for-cli-to-start-the-project

dist/lib/functions/synchronous.js

dist/utils/gh-auth.js

dist/utils/proxy.js

denar90 added 10 commits June 10, 2025 14:14

Add AI command

82710fd

Add login verification functionality

6864489

Add login verification functionality

a403e15

Add clone fucntionality

614fe51

Add navigate

eb21fb0

Improvements

8edaf5f

improve codestyle

1e31e7d

Add MCP to be installed along the process

8633645

Move into init command

775fa44

fixes for parsing

04a41a3

denar90 changed the title ~~Artemdenysov/wrfl 2615 add ai command for cli to start the project~~ (feat): add ai command for cli to start the project Jun 16, 2025

feat: lint and test

6a36601

denar90 marked this pull request as ready for review June 23, 2025 08:44

denar90 requested a review from a team as a code owner June 23, 2025 08:44

denar90 commented Jun 23, 2025

View reviewed changes

eduardoboucas requested changes Jun 23, 2025

View reviewed changes

denar90 and others added 11 commits June 23, 2025 12:30

Update src/commands/init/ai-rules.ts

ad065d7

Co-authored-by: Eduardo Bouças <[email protected]>

Update src/commands/init/ai-rules.ts

4ccd1ba

Co-authored-by: Eduardo Bouças <[email protected]>

Update src/commands/init/ai-rules.ts

127f8b4

Co-authored-by: Eduardo Bouças <[email protected]>

Update src/commands/init/ai-rules.ts

165f6e3

Co-authored-by: Eduardo Bouças <[email protected]>

Update src/commands/init/ai-rules.ts

5285a5d

Co-authored-by: Eduardo Bouças <[email protected]>

code review

983aef7

merge

eb18730

extracting common utils

29228e6

extracting common utils

05b325a

code review

b7bb36c

drop claude file

723222a

denar90 requested a review from eduardoboucas June 23, 2025 10:48

eduardoboucas approved these changes Jun 23, 2025

View reviewed changes

denar90 enabled auto-merge (squash) June 23, 2025 13:38

denar90 added the automerge Add to Kodiak auto merge queue label Jun 23, 2025

sarahetter changed the title ~~(feat): add ai command for cli to start the project~~ feat: add ai command for cli to start the project Jun 23, 2025

denar90 disabled auto-merge June 23, 2025 16:09

denar90 removed the automerge Add to Kodiak auto merge queue label Jun 23, 2025

denar90 marked this pull request as draft June 23, 2025 16:14

Merge remote-tracking branch 'origin/main' into artemdenysov/wrfl-261…

d50b455

…5-add-ai-command-for-cli-to-start-the-project

github-advanced-security bot found potential problems Jun 23, 2025

View reviewed changes

dist/lib/functions/synchronous.js Fixed Show fixed Hide fixed

dist/lib/functions/synchronous.js Fixed Show fixed Hide fixed

dist/utils/gh-auth.js Fixed Show fixed Hide fixed

dist/utils/proxy.js Fixed Show fixed Hide fixed

denar90 force-pushed the artemdenysov/wrfl-2615-add-ai-command-for-cli-to-start-the-project branch from c73cb02 to d50b455 Compare July 11, 2025 09:44

improvements

9e0514f

	export const warn = (message = '') => {
	const bang = chalk.yellow(BANG)
	log(` ${bang} Warning: ${message}`)
	}

feat: add ai command for cli to start the project #7352

Are you sure you want to change the base?

feat: add ai command for cli to start the project #7352

Conversation

denar90 commented Jun 16, 2025

Summary

Uh oh!

github-actions bot commented Jun 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Benchmark results

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

eduardoboucas left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

eduardoboucas Jun 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

denar90 commented Jun 23, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Jun 16, 2025 •

edited

Loading

eduardoboucas Jun 23, 2025 •

edited

Loading