Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -333,6 +333,26 @@ class Colors:
"data-",
"etl",
],
"debug": [
"debug",
"debugging",
"breakpoint",
"logger",
"logging",
"trace",
"profiler",
"profiling",
"devtools",
"inspector",
"monitor",
"troubleshoot",
"diagnostic",
"error-tracking",
"sentry",
"datadog",
"newrelic",
"bugtracking",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add hyphenated bug-tracking keyword

get_category_for_skill normalizes incoming skill names to hyphen-separated text before doing kw in name_lower matching, so a skill named like bug-tracking-* will not match the newly added bugtracking token. In the common case where that skill name does not also contain another debug keyword, it will still fall through to _uncategorized, reducing categorization accuracy for the new debug domain.

Useful? React with 👍 / 👎.

Comment on lines +351 to +354
Copy link

Copilot AI Mar 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

get_category_for_skill() normalizes skill names by replacing underscores with hyphens (name_lower = ...replace("_", "-")). With the current keywords, a skill named new_relic / new-relic (or bug_tracking / bug-tracking, dev_tools / dev-tools) will not match "newrelic" / "bugtracking" / "devtools". Consider adding the hyphen/space variants (e.g., new-relic, bug-tracking, dev-tools, and optionally new relic / bug tracking) so common naming styles categorize correctly.

Copilot uses AI. Check for mistakes.
],
"education": [
"learning",
"course",
Expand Down
Loading