fix(skills): add missing name frontmatter for search-first

[kickbelldev]

Summary

• add missing name: search-first frontmatter to skills/search-first/SKILL.md
• align skill metadata with the expected frontmatter shape used by other skills

Description

Adds the missing name field in the search-first skill frontmatter.

Type

• Skill
• Agent
• Hook
• Command

Type of Change

• fix: Bug fix
• feat: New feature
• refactor: Code refactoring
• docs: Documentation
• test: Tests
• chore: Maintenance/tooling
• ci: CI/CD changes

Testing

• node scripts/ci/validate-skills.js
• npm test

Checklist

• Tests pass locally (node tests/run-all.js)
• Validation scripts pass
• Follows conventional commits format
• Updated relevant documentation
• Follows format guidelines
• Tested with Claude Code
• No sensitive info (API keys, paths)
• Clear descriptions

Summary by CodeRabbit

• Documentation
  • Updated skill metadata configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a name: search-first front matter field to the SKILL.md metadata file. This is a pure metadata addition with no changes to content, logic, or control flow.

Changes

Cohort / File(s)	Summary
Skill Metadata skills/search-first/SKILL.md	Added name: search-first front matter field to skill configuration metadata.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat(skills): add search-first skill #262: Introduces the search-first SKILL.md document that this PR extends with a name field in front matter.

Suggested reviewers

• affaan-m

Poem

🐰 A name field springs forth with grace,
In metadata's small space,
search-first now declared so clear,
This humble change brings cheer! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix(skills): add missing name frontmatter for search-first' accurately and concisely describes the main change: adding a missing name frontmatter field to the search-first skill, aligning it with expected metadata standards.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

skills/search-first/SKILL.md (1)

1-159: Consider adding an explicit ## How It Works section.

The coding guidelines require skills to include sections for "When to Use", "How It Works", and "Examples". The file currently has ## Trigger (covers "When to Use") and ## Examples, but no explicit "How It Works" section — the closest analog is ## Workflow / ## How to Use, which covers the mechanics but doesn't match the required heading. This is a pre-existing gap, not introduced by this PR, but worth addressing.

As per coding guidelines: "Skills should be formatted as Markdown with clear sections for When to Use, How It Works, and Examples."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@skills/search-first/SKILL.md` around lines 1 - 159, Add an explicit "## How
It Works" section to the search-first SKILL.md that describes the core mechanics
of the skill (summarize the 5-step workflow: Need Analysis, Parallel Search,
Evaluate, Decide, Implement), include the Decision Matrix mapping signals to
actions (Adopt/Extend/Compose/Build) and where to invoke the researcher agent
(reference the Task(subagent_type="general-purpose"...) pattern), and place this
new section near the existing "## Workflow" / "## How to Use" content so the
file explicitly contains "When to Use" (Trigger), "How It Works", and "Examples"
headings as required by the coding guidelines.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@skills/search-first/SKILL.md`:
- Around line 1-159: Add an explicit "## How It Works" section to the
search-first SKILL.md that describes the core mechanics of the skill (summarize
the 5-step workflow: Need Analysis, Parallel Search, Evaluate, Decide,
Implement), include the Decision Matrix mapping signals to actions
(Adopt/Extend/Compose/Build) and where to invoke the researcher agent (reference
the Task(subagent_type="general-purpose"...) pattern), and place this new
section near the existing "## Workflow" / "## How to Use" content so the file
explicitly contains "When to Use" (Trigger), "How It Works", and "Examples"
headings as required by the coding guidelines.

[affaan-m]

Automated review: doc-only changes look good. Approving.