fix(devin): give the 11 Devin tools real display names

Every Devin tool had its id as its `name` (`list_session_messages`), so the
generated docs rendered `### list_session_messages` where every other integration
renders a human name. It was the only integration doing this -- 11 of 4427 tools.

Names take the service prefix, matching the majority convention (3200 of 4416
names start with their service).

Also points the ship skill at check:audits instead of hand-listing the audits.
That copy had drifted five behind package.json: cron-parity, import-specifiers,
sql-date-binding, trigger-block-cycle and native-typecheck were all missing, so
shipping never ran them. It was the third copy of that list; there is now one.

Author: waleedlatif1

.agents/skills/ship/SKILL.md

@@ -65,21 +65,10 @@ When the user runs `/ship`:
     echo "❌ block registry audit failed — do not ship"
     exit 1
   }
-  rm -f /tmp/ship-audit-results
-  for s in check:boundaries check:api-validation:strict check:desktop-bridge check:desktop-ipc \
-           check:utils check:zustand-v5 \
-           check:react-query check:client-boundary check:bare-icons check:icon-paths \
-           check:realtime-prune check:tool-registry-boundary check:tool-request-boundary \
-           tool-metadata:check \
-           integration-catalog:check skills:check agent-stream-docs:check; do
-    ( bun run "$s" >"/tmp/ship-audit-${s//:/-}.log" 2>&1; echo "$? $s" >>/tmp/ship-audit-results ) &
-  done
-  wait
-  # any non-zero line is a failing audit — read its /tmp/ship-audit-<name>.log and fix before shipping.
-  # `exit 1` on failure preserves the original sequential checks' semantics (their non-zero exit is
-  # what an agent gates on); never use `grep … && echo ❌ || echo ✅` here — it always exits 0.
-  if grep -vE '^0 ' /tmp/ship-audit-results; then echo "❌ audit(s) failed — do not ship"; exit 1; fi
-  echo "✅ all audits passed"
+  # Runs every audit CI runs, concurrently, and replays the output of any that fail.
+  # Do not hand-list the audits here: the list is derived in scripts/run-audits.ts, and the
+  # copy that used to live in this file had already drifted five audits behind package.json.
+  bun run check:audits || { echo "❌ audit(s) failed — do not ship"; exit 1; }
   ```
   If Phase A regenerated a file, its matching `:check` in Phase B now passes trivially — that parity is the point. Do not ship with any generator or audit failing; fix the cause (never silence it) and re-run. `check:migrations` and `type-check` are covered by steps 5 and CI respectively and are not repeated here.
 7. **Stage and commit** the changes with the generated message — including any files Phase A regenerated in step 6

.claude/commands/ship.md

@@ -64,21 +64,10 @@ When the user runs `/ship`:
     echo "❌ block registry audit failed — do not ship"
     exit 1
   }
-  rm -f /tmp/ship-audit-results
-  for s in check:boundaries check:api-validation:strict check:desktop-bridge check:desktop-ipc \
-           check:utils check:zustand-v5 \
-           check:react-query check:client-boundary check:bare-icons check:icon-paths \
-           check:realtime-prune check:tool-registry-boundary check:tool-request-boundary \
-           tool-metadata:check \
-           integration-catalog:check skills:check agent-stream-docs:check; do
-    ( bun run "$s" >"/tmp/ship-audit-${s//:/-}.log" 2>&1; echo "$? $s" >>/tmp/ship-audit-results ) &
-  done
-  wait
-  # any non-zero line is a failing audit — read its /tmp/ship-audit-<name>.log and fix before shipping.
-  # `exit 1` on failure preserves the original sequential checks' semantics (their non-zero exit is
-  # what an agent gates on); never use `grep … && echo ❌ || echo ✅` here — it always exits 0.
-  if grep -vE '^0 ' /tmp/ship-audit-results; then echo "❌ audit(s) failed — do not ship"; exit 1; fi
-  echo "✅ all audits passed"
+  # Runs every audit CI runs, concurrently, and replays the output of any that fail.
+  # Do not hand-list the audits here: the list is derived in scripts/run-audits.ts, and the
+  # copy that used to live in this file had already drifted five audits behind package.json.
+  bun run check:audits || { echo "❌ audit(s) failed — do not ship"; exit 1; }
   ```
   If Phase A regenerated a file, its matching `:check` in Phase B now passes trivially — that parity is the point. Do not ship with any generator or audit failing; fix the cause (never silence it) and re-run. `check:migrations` and `type-check` are covered by steps 5 and CI respectively and are not repeated here.
 7. **Stage and commit** the changes with the generated message — including any files Phase A regenerated in step 6

.cursor/commands/ship.md

@@ -59,21 +59,10 @@ When the user runs `/ship`:
     echo "❌ block registry audit failed — do not ship"
     exit 1
   }
-  rm -f /tmp/ship-audit-results
-  for s in check:boundaries check:api-validation:strict check:desktop-bridge check:desktop-ipc \
-           check:utils check:zustand-v5 \
-           check:react-query check:client-boundary check:bare-icons check:icon-paths \
-           check:realtime-prune check:tool-registry-boundary check:tool-request-boundary \
-           tool-metadata:check \
-           integration-catalog:check skills:check agent-stream-docs:check; do
-    ( bun run "$s" >"/tmp/ship-audit-${s//:/-}.log" 2>&1; echo "$? $s" >>/tmp/ship-audit-results ) &
-  done
-  wait
-  # any non-zero line is a failing audit — read its /tmp/ship-audit-<name>.log and fix before shipping.
-  # `exit 1` on failure preserves the original sequential checks' semantics (their non-zero exit is
-  # what an agent gates on); never use `grep … && echo ❌ || echo ✅` here — it always exits 0.
-  if grep -vE '^0 ' /tmp/ship-audit-results; then echo "❌ audit(s) failed — do not ship"; exit 1; fi
-  echo "✅ all audits passed"
+  # Runs every audit CI runs, concurrently, and replays the output of any that fail.
+  # Do not hand-list the audits here: the list is derived in scripts/run-audits.ts, and the
+  # copy that used to live in this file had already drifted five audits behind package.json.
+  bun run check:audits || { echo "❌ audit(s) failed — do not ship"; exit 1; }
   ```
   If Phase A regenerated a file, its matching `:check` in Phase B now passes trivially — that parity is the point. Do not ship with any generator or audit failing; fix the cause (never silence it) and re-run. `check:migrations` and `type-check` are covered by steps 5 and CI respectively and are not repeated here.
 7. **Stage and commit** the changes with the generated message — including any files Phase A regenerated in step 6

apps/sim/tools/devin/append_session_tags.ts

@@ -7,7 +7,7 @@ export const devinAppendSessionTagsTool: ToolConfig<
   DevinSessionTagsResponse
 > = {
   id: 'devin_append_session_tags',
-  name: 'append_session_tags',
+  name: 'Devin Append Session Tags',
   description: 'Add tags to a Devin session without removing existing tags (max 50 tags total).',
   version: '1.0.0',
 

apps/sim/tools/devin/archive_session.ts

@@ -7,7 +7,7 @@ export const devinArchiveSessionTool: ToolConfig<
   DevinArchiveSessionResponse
 > = {
   id: 'devin_archive_session',
-  name: 'archive_session',
+  name: 'Devin Archive Session',
   description:
     'Archive a Devin session. Archived sessions can still be viewed but cannot be modified or resumed.',
   version: '1.0.0',

apps/sim/tools/devin/create_session.ts

@@ -8,7 +8,7 @@ export const devinCreateSessionTool: ToolConfig<
   DevinCreateSessionResponse
 > = {
   id: 'devin_create_session',
-  name: 'create_session',
+  name: 'Devin Create Session',
   description:
     'Create a new Devin session with a prompt. Devin will autonomously work on the task described in the prompt.',
   version: '1.0.0',

apps/sim/tools/devin/get_session.ts

@@ -4,7 +4,7 @@ import { DEVIN_SESSION_OUTPUT_PROPERTIES } from './types'
 
 export const devinGetSessionTool: ToolConfig<DevinGetSessionParams, DevinGetSessionResponse> = {
   id: 'devin_get_session',
-  name: 'get_session',
+  name: 'Devin Get Session',
   description:
     'Retrieve details of an existing Devin session including status, tags, pull requests, and structured output.',
   version: '1.0.0',

apps/sim/tools/devin/get_session_tags.ts

@@ -6,7 +6,7 @@ export const devinGetSessionTagsTool: ToolConfig<
   DevinSessionTagsResponse
 > = {
   id: 'devin_get_session_tags',
-  name: 'get_session_tags',
+  name: 'Devin Get Session Tags',
   description: 'Retrieve the tags currently applied to a Devin session.',
   version: '1.0.0',
 

apps/sim/tools/devin/list_session_attachments.ts

@@ -10,7 +10,7 @@ export const devinListSessionAttachmentsTool: ToolConfig<
   DevinListSessionAttachmentsResponse
 > = {
   id: 'devin_list_session_attachments',
-  name: 'list_session_attachments',
+  name: 'Devin List Session Attachments',
   description: 'List the files uploaded to or produced by a Devin session.',
   version: '1.0.0',
 

apps/sim/tools/devin/list_session_messages.ts

@@ -7,7 +7,7 @@ export const devinListSessionMessagesTool: ToolConfig<
   DevinListSessionMessagesResponse
 > = {
   id: 'devin_list_session_messages',
-  name: 'list_session_messages',
+  name: 'Devin List Session Messages',
   description:
     'List the messages exchanged in a Devin session, including messages from both the user and Devin.',
   version: '1.0.0',