appleboy/skills

1. This repository is not an application runtime; it is a collection of Claude Code skills/plugins packaged for distribution through a Claude marketplace. The architecture is content-first: mostly manifests and Markdown skill definitions rather than executable code.

2. The root marketplace layer is .claude-plugin/marketplace.json, which acts as the catalog entrypoint for the whole repo. It is the boundary a Claude Code client uses to discover installable plugins under plugins/.

3. Each item under plugins/ is an independent plugin unit with its own .claude-plugin/plugin.json manifest and one skill document in skills/<skill-name>/SKILL.md. That makes each plugin a separately installable, loosely coupled module.

4. The plugin set is organized by workflow stage:

- commit-message for conventional commit generation from staged git changes

- classify-change for deciding leaf vs core change scope

- plan-feature for pre-coding feature planning and plan.md handoff

- pr-prepare for PR description drafting and checklisting

- code-review and copilot-review for review workflows

- prompt-audit for improving prompts against a rubric

5. The skill files are the behavioral core. SKILL.md likely contains the instructions, heuristics, and output format the Claude agent follows. In diagram terms, this is where the “logic” lives, but it is declarative content rather than code.

6. The main data flow is:

user invokes a plugin in Claude Code → marketplace resolves plugin manifest → plugin manifest points to the skill document → Claude loads the skill instructions and applies them to the current context.

The inputs are typically git state, PR diffs, prompts, or repository context; the outputs are commit messages, plans, reviews, or rewritten prompts.

7. A key architectural boundary is between classification/planning skills and execution/review skills. classify-change and plan-feature decide scope and approach before work starts, while code-review, copilot-review, and pr-prepare operate after code or PR content exists.

8. Another boundary is human-facing artifact generation. Several skills are designed to produce concrete handoff artifacts outside the plugin system: commit messages, PR descriptions, review comments, and plan.md. The repo is therefore a workflow accelerator, not a source of product business logic.

9. Tooling and release infrastructure are lightweight but important:

- .github/workflows/goreleaser.yml and .goreleaser.yaml handle packaging/release automation

- .github/workflows/security.yml runs security scanning

- Dependabot and funding metadata support maintenance

These files suggest the repo is distributed as a versioned plugin bundle.

10. The external dependency is primarily the Claude Code plugin ecosystem itself, with GitHub as the hosting/release platform. There is no sign of a backend service, database, or API layer; the runtime is the user’s Claude Code environment consuming packaged skill definitions from this repository.