core/agent
8
0
Fork 0
Code Issues 5 Pull requests Projects Releases Packages Wiki Activity Actions
agent/plugins/core-php/commands/commit.md
Snider 55bc34c885 feat(agent/plugins): create plugins/{core-go,core-php,infra} tree (RFC.plugin-restructure §1+§2) 
plugins/ subtree created from scratch (no dappcore-go/dappcore-php
existed to rename). Per docs/RFC-AGENT-PLUGIN-RESTRUCTURE.md:

plugins/core-go/:
- .claude-plugin/plugin.json (name: core-go)
- README.md, marketplace.yaml, .mcp.json (calls core mcp serve)
- commands/{commit,qa,review,verify}.md
- skills/{core,core-go,go-agent}/SKILL.md (seeded from existing repo material)
- skills/api-endpoints/SKILL.md (NEW per ticket)
- agents/go-developer.md
- hook scripts referenced by commands

plugins/core-php/: same structure, php-developer agent + php-specific
api-endpoints skill.

plugins/infra/: plugin.json, README.md, marketplace.yaml, agents/infra-ops.md.

Manifests use core-* not dappcore-*. .mcp.json files call core mcp serve.
No dappcore-* names left.

Note: seed skills copied from existing repo material per ticket spec —
some upstream Host UK examples remain in copied skill docs. Future PR
can purge those if Host UK references are out of scope for the public
plugin marketplace.

Co-authored-by: Codex <noreply@openai.com>
Closes tasks.lthn.sh/view.php?id=234
2026-04-25 20:05:05 +01:00

1.4 KiB
Raw Blame History

name description args flags hooks
commit Generate a conventional commit message for staged changes [message]
--amend
Before
hooks
type command
command ${CLAUDE_PLUGIN_ROOT}/scripts/smart-commit.sh

Smart Commit

Generate a conventional commit message for staged changes.

Usage

Generate message automatically: /core-php:commit

Provide a custom message: /core-php:commit "feat(module): add action validation"

Amend the previous commit: /core-php:commit --amend

Behavior

  1. Analyze Staged Changes: Examines the git diff --staged to understand the nature of the changes.
  2. Generate Conventional Commit Message:
    • feat: For new files, functions, or features.
    • fix: For bug fixes.
    • refactor: For code restructuring without changing external behavior.
    • docs: For changes to documentation.
    • test: For adding or modifying tests.
    • chore: For routine maintenance tasks.
  3. Determine Scope: Infers the scope from the affected module's file paths (e.g., auth, payment, ui).
  4. Add Co-Authored-By Trailer: Appends Co-Authored-By: Claude <noreply@anthropic.com> to the commit message.

Message Generation Example

feat(auth): add JWT token validation

- Add validateToken() function
- Add token expiry check
- Add unit tests for validation

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