Skip to content

refactor(skills): sweep agent-agnostic phrasing across Tier-1/featured#40

Merged
naimkatiman merged 1 commit intomainfrom
feat/agent-agnostic-skills-sweep
Apr 28, 2026
Merged

refactor(skills): sweep agent-agnostic phrasing across Tier-1/featured#40
naimkatiman merged 1 commit intomainfrom
feat/agent-agnostic-skills-sweep

Conversation

@naimkatiman
Copy link
Copy Markdown
Owner

Summary

Follow-up to #38. Same low-risk Claude→agent phrasing-only refactor, applied across the next batch of skills:

  • gateguard ×2 (forces Claude → forces the agent; Claude tends to guess → the agent tends to guess)
  • token-budget-advisor ×1 (before Claude answers → before the agent answers)
  • verification-loop ×2 (description + prose: Claude Code sessions → agent coding sessions)
  • strategic-compact ×1 (CLAUDE.md instructionsAgent instructions (from CLAUDE.md / AGENTS.md))
  • skills/README.md ×2 (Claude's recommendation list → the agent's recommendation list; any Claude recommendation list → any agent recommendation list)

Files

  • 5 source files in skills/
  • 5 mirror files in plugins/continuous-improvement/skills/ (regenerated by npm run build per the bin/generate-plugin-manifests.mjs pipeline; the source skills/README.md says these mirrors are auto-generated)

10 files total, +15 / -15. Within the 15-file commit-size gate.

Out of scope (deliberately left alone)

  • proceed-with-the-recommendation — already covered by refactor(skill): make proceed-with-the-recommendation agent-agnostic #38
  • workspace-surface-audit — most Claude references are legitimate product references (set up Claude Code trigger phrase, Claude or Codex plugins audit list, AGENTS.md, CLAUDE.md install-config path list). Deferred to a separate, more careful audit.
  • ralph — both Claude references are legitimate (section header # Using Claude Code, file path scripts/ralph/CLAUDE.md)
  • token-budget-advisor.md line 133 attribution to the upstream "Token Budget Advisor for Claude Code" project (proper noun, not generic phrasing)

Test plan

  • Local npm test: 238/238 pass (build + tests)
  • check-skill-mirror.test.mjs passes (source + mirror byte-identical after regen)
  • CI green on Node 18 / 20 / 22 + lint-transcript

Replace Claude-specific phrasing with neutral "agent" terminology
across gateguard, token-budget-advisor, verification-loop,
strategic-compact, and the source skills README so these skills are
invocable from any AI coding agent (Claude, Codex, Gemini, etc.).

Source files (5) + plugin mirror (5, regenerated via npm run build).
Phrasing-only refactor; no behavior change. 238/238 tests pass.

Out of scope:
- proceed-with-the-recommendation (covered by PR #38)
- workspace-surface-audit (most matches are legitimate product
  references; deferred to a separate audit)
- ralph (both Claude references are legitimate: section header for
  Claude Code usage and the literal scripts/ralph/CLAUDE.md path)
- token-budget-advisor.md attribution line ("Token Budget Advisor for
  Claude Code" is the original project name)
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates several documentation files and skill descriptions to replace specific references to "Claude" and "Claude Code" with more generic terminology such as "agent" and "agent coding sessions." A review comment identifies a minor phrasing inconsistency in skills/README.md and provides a suggestion to use "agent" as an adjective for better alignment with the rest of the changes.

Comment thread skills/README.md
| Skill | What it does | Source |
|-------|--------------|--------|
| **`proceed-with-the-recommendation`** ⭐ | Walks any Claude recommendation list top-to-bottom under the 7 Laws — routes each item to the right specialist (`superpowers:*`, `ralph`, `workspace-surface-audit`, `simplify`, `security-review`, `schedule`, `loop`), falls back to inline behavior when a specialist isn't installed, verifies per item, halts on `needs-approval` | @naimkatiman |
| **`proceed-with-the-recommendation`** ⭐ | Walks any agent's recommendation list top-to-bottom under the 7 Laws — routes each item to the right specialist (`superpowers:*`, `ralph`, `workspace-surface-audit`, `simplify`, `security-review`, `schedule`, `loop`), falls back to inline behavior when a specialist isn't installed, verifies per item, halts on `needs-approval` | @naimkatiman |
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The phrasing "any agent's recommendation list" is slightly inconsistent with the original "any Claude recommendation list" (where "Claude" was used as an adjective) and deviates from the intended change described in the PR summary ("any agent recommendation list"). Using "agent" as an adjective here would be more consistent with the rest of the refactor and the original phrasing style.

Suggested change
| **`proceed-with-the-recommendation`**| Walks any agent's recommendation list top-to-bottom under the 7 Laws — routes each item to the right specialist (`superpowers:*`, `ralph`, `workspace-surface-audit`, `simplify`, `security-review`, `schedule`, `loop`), falls back to inline behavior when a specialist isn't installed, verifies per item, halts on `needs-approval` | @naimkatiman |
| **`proceed-with-the-recommendation`**| Walks any agent recommendation list top-to-bottom under the 7 Laws — routes each item to the right specialist (`superpowers:*`, `ralph`, `workspace-surface-audit`, `simplify`, `security-review`, `schedule`, `loop`), falls back to inline behavior when a specialist isn't installed, verifies per item, halts on `needs-approval` | @naimkatiman |

@naimkatiman naimkatiman merged commit 14cb86b into main Apr 28, 2026
4 checks passed
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