@codeam/shared 2.61.21 → 2.61.23

package/dist/index.mjs

@@ -801,6 +801,17 @@ var INTEGRATION_BRANDING = {
     brandColor: "#FFFFFF",
     logoSvg: '<svg role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><title>GitHub</title><path fill="#FFFFFF" d="M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12"/></svg>'
   },
+  // npm — a brand-only entry (NOT an `IntegrationId`): the registry the
+  // codeam-cli ships to. Present so surfaces like the Wiki can render the
+  // official npm mark from the ONE shared catalog instead of a loose asset.
+  npm: {
+    id: "npm",
+    name: "npm",
+    vendor: "npm, Inc.",
+    tagline: "The Node package registry",
+    brandColor: "#CB3837",
+    logoSvg: '<svg role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><title>npm</title><path fill="#CB3837" d="M1.763 0C.786 0 0 .786 0 1.763v20.474C0 23.214.786 24 1.763 24h20.474c.977 0 1.763-.786 1.763-1.763V1.763C24 .786 23.214 0 22.237 0zM5.13 5.323l13.837.019-.009 13.836h-3.464l.01-10.382h-3.456L12.08 19.17H5.113z"/></svg>'
+  },
   jira: {
     // Branding key kept 'jira' for id-stability; DISPLAY rebranded to Atlassian
     // (the one integration fronts both Jira + Confluence via mcp-atlassian).
@@ -1011,6 +1022,94 @@ function getIntegrationBranding(id) {
   return INTEGRATION_BRANDING[id] ?? null;
 }
 
+// src/skills/registry.ts
+var CODE_REVIEW_BODY = `Use this skill when reviewing a pull request. It defines what a high-signal
+review looks like so your inline comments are worth the author's time.
+
+## Review priorities (in order)
+1. **Correctness** \u2014 does the change do what the PR says, and only that? Trace the
+   changed paths for logic errors, off-by-one, null/undefined, wrong branch, and
+   inverted conditions. State a concrete failure scenario (inputs \u2192 wrong output)
+   for anything you flag as a bug.
+2. **Security** \u2014 untrusted input reaching a sink (SQL, shell, path, HTML), secrets
+   in code/logs, authz gaps, credentials passed via argv instead of env.
+3. **Tests** \u2014 does the change carry tests that would fail without it? Missing
+   coverage on a bug-prone path is a finding.
+4. **Clarity / reuse** \u2014 duplicated logic, a simpler existing helper, a name that
+   misleads. Only raise these when they materially affect maintainability.
+
+## Comment discipline
+- One finding per comment, anchored to the exact line.
+- Lead with severity: **blocker**, **should-fix**, or **nit**.
+- Say WHY (the failure or risk), not just WHAT. Propose the fix when it is short.
+- Do NOT restate the diff, praise trivially, or nitpick style a formatter owns.
+- If the PR is correct and well-tested, say so plainly and approve \u2014 a clean review
+  is a valid outcome, not a failure to find something.
+
+## Scope
+Review only what the diff changes and its direct blast radius. Do not demand
+unrelated refactors.`;
+var CODE_REVIEW_INSTRUCTION = `When reviewing this PR, prioritize correctness first, then security, then test
+coverage, then clarity/reuse. One finding per inline comment, anchored to the exact
+line, each led by a severity tag (blocker/should-fix/nit) and a concrete reason
+(the failure scenario or risk), not a restatement of the diff. If the change is
+correct and well-tested, approve and say so \u2014 finding nothing is a valid outcome.
+Review only the diff and its direct blast radius; do not demand unrelated refactors.`;
+var RESOLVE_CONFLICTS_BODY = `Use this skill when resolving merge conflicts on a pull request. The goal is a
+merge that preserves BOTH sides' intent, not one that just makes the file compile.
+
+## Method
+1. Understand each conflict hunk before editing: what did HEAD change, what did the
+   base branch change, and WHY. Read the surrounding function, not just the markers.
+2. Prefer a union of intents. Drop a side only when the two changes are genuinely
+   mutually exclusive \u2014 and when you do, keep the side that matches the PR's purpose.
+3. Never leave a conflict marker (\`<<<<<<<\`, \`=======\`, \`>>>>>>>\`) behind. Grep for
+   them before committing.
+4. After resolving, the code must build and its tests must pass. Run them. A merge
+   that resolves markers but breaks the build is not done.
+5. For lockfiles/generated files, regenerate rather than hand-merge.
+
+## Commit
+One commit that explains what was reconciled and any intent you had to choose
+between. Then push the branch.`;
+var RESOLVE_CONFLICTS_INSTRUCTION = `When resolving these merge conflicts, preserve both sides' intent \u2014 read each hunk's
+surrounding code to understand what HEAD and the base branch each changed and why,
+and prefer a union of intents; drop a side only when the two are mutually exclusive,
+keeping the side that matches the PR's purpose. Leave no conflict markers behind
+(grep for them). Regenerate lockfiles rather than hand-merging them. The result must
+build and pass tests \u2014 run them \u2014 before you commit and push.`;
+var SKILL_REGISTRY = {
+  "code-review": {
+    id: "code-review",
+    name: "Code Review",
+    description: `High-signal PR review: prioritize correctness \u2192 security \u2192 tests \u2192 clarity, one anchored finding per comment.`,
+    source: "curated",
+    delivery: {
+      skillFile: { body: CODE_REVIEW_BODY },
+      instruction: { body: CODE_REVIEW_INSTRUCTION }
+    }
+  },
+  "resolve-conflicts": {
+    id: "resolve-conflicts",
+    name: "Resolve Conflicts",
+    description: `Merge-conflict resolution that preserves both sides' intent, leaves no markers, and keeps the build green.`,
+    source: "curated",
+    delivery: {
+      skillFile: { body: RESOLVE_CONFLICTS_BODY },
+      instruction: { body: RESOLVE_CONFLICTS_INSTRUCTION }
+    }
+  }
+};
+function isSkillId(id) {
+  return Object.prototype.hasOwnProperty.call(SKILL_REGISTRY, id);
+}
+function getSkillDefinition(id) {
+  return isSkillId(id) ? SKILL_REGISTRY[id] : null;
+}
+function skillHasRail(id, rail) {
+  return Boolean(SKILL_REGISTRY[id].delivery[rail]);
+}
+
 // src/api-url.ts
 var DEFAULT_API_BASE_URL = "https://api.codeagent-mobile.com";
 var DEV_API_BASE_URL = "https://dev-api.codeagent-mobile.com";
@@ -1222,6 +1321,7 @@ export {
   PREVIEW_DETECT_PROMPT,
   PROTOCOL_VERSION,
   PUBLIC_TO_INTERNAL,
+  SKILL_REGISTRY,
   SSE_SOCKET_TIMEOUT_MS,
   TERMINAL_AGENT_PREFIX,
   UNKNOWN_MODEL_PRICING,
@@ -1235,6 +1335,7 @@ export {
   getIntegrationBranding,
   getIntegrationsByCategory,
   getPricing,
+  getSkillDefinition,
   headroomKindFor,
   headroomModelPredownloadScript,
   headroomPipPackage,
@@ -1245,10 +1346,12 @@ export {
   isKnownIntegrationId,
   isKnownModel,
   isLinkedAgentId,
+  isSkillId,
   normalizeAgentId,
   publicToInternal,
   renderToLines,
   resolveApiBaseUrl,
+  skillHasRail,
   toRemoteCommand,
   tryGetContextWindow
 };