Skip to content

Update TensorRT-LLM skill count from 4 to 20#4

Merged
mosheabr merged 1 commit into
mainfrom
fix-trtllm-count
Apr 9, 2026
Merged

Update TensorRT-LLM skill count from 4 to 20#4
mosheabr merged 1 commit into
mainfrom
fix-trtllm-count

Conversation

@mosheabr
Copy link
Copy Markdown
Collaborator

@mosheabr mosheabr commented Apr 9, 2026

TensorRT-LLM added 16 new skills upstream. Updated README count and description.

New skills: performance analysis/optimization, kernel writing (CUTE, TileIR, Triton), Nsight profiling, code contribution, codebase exploration.

Note: CI expected count in ci.yml also needs updating (4→20) but requires workflow scope to push. Will follow up separately.

TensorRT-LLM added 16 new skills upstream: performance analysis/optimization,
kernel writing (CUTE, TileIR, Triton), Nsight profiling, code contribution,
and codebase exploration.

Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
@mosheabr mosheabr merged commit 0eff618 into main Apr 9, 2026
1 check failed
mosheabr added a commit that referenced this pull request Jun 4, 2026
#2 (MED) — gh issue create can skip tracker on bad assignee:
  The "Track dropped skills" step has continue-on-error: true, so a
  bad assignee wouldn't kill the whole sync — but it would skip
  tracker creation entirely, defeating the feature. Both branches
  (edit existing / create new) now follow the same tolerant pattern:
  create-without-assignees first, then loop --add-assignee in a
  trim + per-handle warning. A typo in CATALOG_TRACKER_ASSIGNEES no
  longer blocks the tracker from existing.

#3 (LOW) — Hardcoded personal fallback:
  Reworked per Codex's catch that GitHub issue assignees are users,
  not teams — so the earlier "use a team handle" comment was wrong.
  If CATALOG_TRACKER_ASSIGNEES is unset we now skip assignment
  entirely and emit a ::warning title=Drift notifications inactive::.
  No personal fallback; a deactivated handle would silently mute
  notifications. The warning surfaces in the workflow log every run
  until the secret is set.

#4 (LOW / clarification) — Deleted-sig case:
  Added an inline comment in the drift loop noting that an rsync
  that deletes skill.oms.sig alongside content edits registers the
  deletion in `git diff` (sig_changed matches → drift NOT flagged
  here), and the now-sigless skill falls through to the compliance
  step under "missing artifacts: skill.oms.sig". Defense in depth.

#1 (HIGH per Sayali) — README version inconsistency on revert:
  NOT addressed in this commit — verified against
  .github/scripts/regenerate-readme.sh on main: the README table
  is now "Product | Description | Skills" (PR #215, commit 1104de0
  on 2026-06-01 dropped the Source + Version columns). VERSIONS_FILE
  is declared but never consumed, and /tmp/sync-versions.txt is
  vestigial. So the exact "README will lie" risk Sayali raised is
  stale. Plan to send her the context separately and open a small
  follow-up PR to drop the dead sync-versions write + VERSIONS_FILE
  declaration so this trap doesn't catch a future reader.

Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant