Skip to content

Commit 12255f8

Browse files
author
Mitsuyuki Osabe
committed
fix: add comment for check ordering + sync skills-status eligibility
- Add comment explaining why enabled: true is checked after isBundledSkillAllowed (Greptile review feedback). - Sync skills-status.ts eligibility with force-enable: when enabled: true, mark the skill as eligible in status reporting so CLI output matches runtime behavior (Codex review feedback). ✍️ Author: Claude Code with @carrotRakko (AI-written, human-approved)
1 parent 9f7b118 commit 12255f8

2 files changed

Lines changed: 5 additions & 1 deletion

File tree

src/agents/skills-status.ts

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -200,7 +200,8 @@ function buildSkillStatus(
200200
isEnvSatisfied,
201201
isConfigSatisfied,
202202
});
203-
const eligible = !disabled && !blockedByAllowlist && requirementsSatisfied;
203+
const forceEnabled = skillConfig?.enabled === true;
204+
const eligible = !disabled && !blockedByAllowlist && (forceEnabled || requirementsSatisfied);
204205

205206
return {
206207
name: entry.skill.name,

src/agents/skills/config.ts

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,9 @@ export function shouldIncludeSkill(params: {
8484
if (!isBundledSkillAllowed(entry, allowBundled)) {
8585
return false;
8686
}
87+
// enabled: true force-enables, bypassing runtime eligibility (bins, OS, etc.).
88+
// Placed after isBundledSkillAllowed so allowBundled still gates bundled skills.
89+
// enabled: false short-circuits before that check since the result is the same.
8790
if (skillConfig?.enabled === true) {
8891
return true;
8992
}

0 commit comments

Comments
 (0)