mirror of https://github.com/secondsky/claude-skills.git synced 2026-09-18 19:54:22 +08:00

Files

T

secondsky c1afc6db8b refactor: Flatten plugin structure to fix skill discovery (v3.2.0)

BREAKING CHANGE: All plugin paths changed from nested to flat structure

Problem:
- Only 11 out of 169 skills appeared in Claude Code's system prompt
- v3.1.0 updated marketplace.json but didn't migrate directory structure
- Mismatch: marketplace expected `./plugins/skill-name` but files were at
  `./plugins/category/skills/skill-name`

Solution:
- Moved all 169 skills from `plugins/*/skills/*` to `plugins/*` (flat)
- Removed 66 empty category directories (api, cloudflare, testing, etc.)
- Updated marketplace.json with correct flat paths (all 169 entries)
- Updated scripts to work with flat structure:
  - generate-marketplace.sh: removed nested loop logic
  - sync-plugins.sh: simplified to single loop
  - Added flatten-plugin-structure.sh migration tool

Migration Details:
- Used git mv to preserve history for all 169 skills
- Handled name collisions via temporary directories
- Validated: 0 errors, 169 skills successfully migrated

Results:
- ✅ All 169 skills at `plugins/*/` level
- ✅ marketplace.json: 169 valid entries
- ✅ No nested skills/ directories remain
- ✅ Scripts updated and tested

This completes the migration started in v3.1.0 (commit 677abf8) and
resolves skill discovery issues.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2025-12-24 02:03:18 +01:00

1.7 KiB

Raw Permalink Blame History

Code Review Skill

Technical rigor and evidence-based practices for code review workflows.

Overview

This skill guides proper code review practices emphasizing technical correctness over social comfort, evidence-based claims, and verification before completion. It covers receiving feedback, requesting reviews, and implementing verification gates.

Core Practices

Receiving Feedback - Technical evaluation over performative agreement
Requesting Reviews - Systematic review via code-reviewer subagent
Verification Gates - Evidence before any completion claims

When to Use

Receiving code review comments (unclear or technically questionable)
Completing tasks or major features requiring review
Before making any completion/success claims
Before committing, pushing, or creating PRs
Subagent-driven development workflows

Key Principles

NO performative agreement - No "Great point!" or "You're absolutely right!"
Verify before implementing - Check suggestions against codebase reality
Evidence before claims - Run verification commands, read output, THEN claim
Push back when wrong - Technical correctness over social comfort

Reference Files

references/code-review-reception.md - Receiving feedback protocol
references/requesting-code-review.md - How to request reviews
references/verification-before-completion.md - Verification gates

Auto-Trigger Keywords

code review
pull request review
technical feedback
verification gates
completion claims
subagent review
merge requirements
evidence-based development

Source

Adapted from mrgoonie/claudekit-skills

1.7 KiB Raw Permalink Blame History