fix: remove add-oauth subcommand and fix skill issues from code review

- Remove add-oauth subcommand and pipedrive-add-oauth skill (OAuth is always
  included in the scaffold, making the addon redundant)
- Fix docker-compose template in add-app-extension skill to match actual
  generated output (Dockerfile.app-extension-ui, correct service config)
- Fix stale src/pipedrive-client/ path in pipedrive-api skill (now src/pipedrive/)
- Replace rg with grep in Codex marketplace-readiness-checks reference

Author: dmitriyeff

CLAUDE.md

@@ -45,7 +45,6 @@ The CLI asks for:
 Beyond the interactive main flow, the CLI supports subcommands invoked by the AI plugin skills:
 
 ```bash
-npx create-pipedrive-app add-oauth [--output-dir <dir>]
 npx create-pipedrive-app add-app-extension --app-extensions custom-panel|custom-modal [--output-dir <dir>]
 ```
 
@@ -159,7 +158,6 @@ The `plugin/` directory is shipped with the npm package (`"files": ["dist", "plu
 | Skill | Purpose |
 |-------|---------|
 | `pipedrive-new-app` | Scaffold a new app interactively via `npx create-pipedrive-app` |
-| `pipedrive-add-oauth` | Add OAuth to an existing project via the `add-oauth` subcommand |
 | `pipedrive-add-app-extension` | Add a panel or modal extension via the `add-app-extension` subcommand |
 | `pipedrive-api` | Guide on using the Pipedrive REST API and SDK within a generated project |
 | `pipedrive-review-marketplace-readiness` | Gap analysis before marketplace submission: checks token refresh, HTTPS, error handling, and rate limit handling |

README.md

@@ -81,7 +81,6 @@ Both plugins expose the same slash commands:
 | Command | What it does |
 |---------|-------------|
 | `/pipedrive-new-app` | Scaffold a new integration project |
-| `/pipedrive-add-oauth` | Add OAuth to an existing project |
 | `/pipedrive-add-app-extension` | Add a custom panel or modal extension |
 | `/pipedrive-api` | Get guidance on using the Pipedrive API |
 | `/pipedrive-review-marketplace-readiness` | Check for gaps before submitting to the marketplace |

plugin/skills/pipedrive-add-app-extension/SKILL.md

@@ -67,20 +67,56 @@ Read `frontend/app-extension-ui/src/main.tsx`. If the App Extensions frontend al
 
 ## Update docker-compose.yml
 
-Read `docker-compose.yml`. If it does not already contain a `vite` or `frontend` service definition, add the Vite dev service. Model it after the service generated for a full scaffold:
+Read `docker-compose.yml`. If it does not already contain an `app-extension-ui` service, add it under `services:` and add `app_extension_ui_node_modules:` under `volumes:`:
 
 ```yaml
-  frontend:
+services:
+  app-extension-ui:
     build:
       context: .
-      target: frontend-dev
+      dockerfile: Dockerfile.app-extension-ui
+    user: root
+    command: sh -c "chown -R node:node /app/node_modules && su-exec node sh -c 'echo Installing dependencies... && npm install --no-package-lock --no-audit --no-fund --loglevel=error && npm run dev:frontend'"
+    environment:
+      CHOKIDAR_USEPOLLING: "true"
     ports:
       - "5173:5173"
+    volumes:
+      - ./package.json:/app/package.json:ro
+      - app_extension_ui_node_modules:/app/node_modules
     develop:
       watch:
         - action: sync
-          path: ./frontend
-          target: /app/frontend
+          path: ./frontend/app-extension-ui
+          target: /app/frontend/app-extension-ui
+          initial_sync: true
+          ignore:
+            - node_modules/
+            - dist/
+        - action: rebuild
+          path: ./package.json
+
+volumes:
+  app_extension_ui_node_modules:
+```
+
+Also create `Dockerfile.app-extension-ui` in the project root if it does not exist:
+
+```dockerfile
+FROM node:24-alpine
+
+RUN apk add --no-cache su-exec
+WORKDIR /app
+ENV NPM_CONFIG_USERCONFIG=/tmp/.npmrc
+RUN mkdir -p /app/node_modules && chown -R node:node /app
+USER node
+RUN npm config set registry https://registry.npmjs.org/
+
+COPY --chown=node:node package.json ./
+COPY --chown=node:node frontend/app-extension-ui ./frontend/app-extension-ui
+
+EXPOSE 5173
+CMD ["npm", "run", "dev:frontend"]
 ```
 
 ## Report to developer

plugin/skills/pipedrive-add-oauth/SKILL.md

@@ -12,7 +12,7 @@ The Pipedrive REST API v1 base URL is `https://api.pipedrive.com/v1`. It is stat
 
 ## Authentication in this project
 
-This project uses **OAuth 2.0**. After a user authorises your app, the access token is stored in the database (`pipedrive_tokens` table). The generated `src/pipedrive-client/` module handles token retrieval and client initialisation:
+This project uses **OAuth 2.0**. After a user authorises your app, the access token is stored in the database (`pipedrive_tokens` table). The generated `src/pipedrive/` module handles token retrieval and client initialisation:
 
 ```ts
 import { getClient } from './pipedrive/client.js';
@@ -55,7 +55,7 @@ await client.activities.addActivity({
 
 ## Adding a new API call
 
-1. Read `src/pipedrive-client/` to understand the existing wrapper pattern
+1. Read `src/pipedrive/` to understand the existing wrapper pattern
 2. Use `client.<resource>.<method>()` following the SDK method names
 3. Handle token expiry — the client wrapper in this project manages token refresh automatically
 

plugin/skills/pipedrive-api/SKILL.md

@@ -60,20 +60,56 @@ Read `frontend/app-extension-ui/src/main.tsx`. If the App Extensions frontend al
 
 ## Update docker-compose.yml
 
-Read `docker-compose.yml`. If it does not already contain a `vite` or `frontend` service definition, add the Vite dev service. Model it after the service generated for a full scaffold:
+Read `docker-compose.yml`. If it does not already contain an `app-extension-ui` service, add it under `services:` and add `app_extension_ui_node_modules:` under `volumes:`:
 
 ```yaml
-  frontend:
+services:
+  app-extension-ui:
     build:
       context: .
-      target: frontend-dev
+      dockerfile: Dockerfile.app-extension-ui
+    user: root
+    command: sh -c "chown -R node:node /app/node_modules && su-exec node sh -c 'echo Installing dependencies... && npm install --no-package-lock --no-audit --no-fund --loglevel=error && npm run dev:frontend'"
+    environment:
+      CHOKIDAR_USEPOLLING: "true"
     ports:
       - "5173:5173"
+    volumes:
+      - ./package.json:/app/package.json:ro
+      - app_extension_ui_node_modules:/app/node_modules
     develop:
       watch:
         - action: sync
-          path: ./frontend
-          target: /app/frontend
+          path: ./frontend/app-extension-ui
+          target: /app/frontend/app-extension-ui
+          initial_sync: true
+          ignore:
+            - node_modules/
+            - dist/
+        - action: rebuild
+          path: ./package.json
+
+volumes:
+  app_extension_ui_node_modules:
+```
+
+Also create `Dockerfile.app-extension-ui` in the project root if it does not exist:
+
+```dockerfile
+FROM node:24-alpine
+
+RUN apk add --no-cache su-exec
+WORKDIR /app
+ENV NPM_CONFIG_USERCONFIG=/tmp/.npmrc
+RUN mkdir -p /app/node_modules && chown -R node:node /app
+USER node
+RUN npm config set registry https://registry.npmjs.org/
+
+COPY --chown=node:node package.json ./
+COPY --chown=node:node frontend/app-extension-ui ./frontend/app-extension-ui
+
+EXPOSE 5173
+CMD ["npm", "run", "dev:frontend"]
 ```
 
 ## Report to developer

plugins/create-pipedrive-app/skills/pipedrive-add-app-extension/SKILL.md

@@ -12,7 +12,7 @@ The Pipedrive REST API v1 base URL is `https://api.pipedrive.com/v1`. It is stat
 
 ## Authentication in this project
 
-This project uses **OAuth 2.0**. After a user authorises your app, the access token is stored in the database (`pipedrive_tokens` table). The generated `src/pipedrive-client/` module handles token retrieval and client initialisation:
+This project uses **OAuth 2.0**. After a user authorises your app, the access token is stored in the database (`pipedrive_tokens` table). The generated `src/pipedrive/` module handles token retrieval and client initialisation:
 
 ```ts
 import { getClient } from './pipedrive/client.js';
@@ -49,7 +49,7 @@ await client.activities.addActivity({
 
 ## Adding a new API call
 
-1. Read `src/pipedrive-client/` to understand the existing wrapper pattern
+1. Read `src/pipedrive/` to understand the existing wrapper pattern
 2. Use `client.<resource>.<method>()` following the SDK method names
 3. Handle token expiry — the client wrapper in this project manages token refresh automatically
 

plugins/create-pipedrive-app/skills/pipedrive-add-oauth/SKILL.md

@@ -15,7 +15,7 @@ Collect every failure before reporting.
 Run:
 
 ```bash
-rg -n "Authorization|Bearer|access_token" src -g "*.ts" -g "!src/pipedrive/client.ts"
+grep -rn "Authorization\|Bearer\|access_token" src --include="*.ts" | grep -v "src/pipedrive/client.ts"
 ```
 
 Review each direct `fetch(` or `axios` call with an Authorization header.
@@ -42,8 +42,8 @@ Fix: Use `getClient(companyId)` from `src/pipedrive/client.ts`, or add a 401 ret
 Run:
 
 ```bash
-rg -n "http://" src -g "*.ts"
-rg -n "trust proxy" src/app.ts
+grep -rn "http://" src --include="*.ts"
+grep -n "trust proxy" src/app.ts
 ```
 
 Fail if any production URL uses `http://`; ignore localhost and 127.0.0.1.
@@ -61,8 +61,8 @@ Report hardcoded HTTP URLs with file and line. For missing proxy trust, tell the
 Run:
 
 ```bash
-rg -n "NextFunction" src/app.ts
-rg -n "async.*req.*res" src -g "*.ts"
+grep -n "NextFunction" src/app.ts
+grep -rn "async.*req.*res" src --include="*.ts"
 ```
 
 Fail if `src/app.ts` has no 4-argument Express error middleware like:
@@ -83,7 +83,7 @@ Report each missing handler by file and line, and tell the developer to wrap the
 Run:
 
 ```bash
-rg -n "429|X-RateLimit|Retry-After" src -g "*.ts"
+grep -rn "429\|X-RateLimit\|Retry-After" src --include="*.ts"
 ```
 
 Fail if there is no handling for Pipedrive API rate limits. Pipedrive returns HTTP 429 and rate-limit headers including `X-RateLimit-Limit`, `X-RateLimit-Remaining`, and `X-RateLimit-Reset`.