Skip to content

Ecc tools/agent plugins 1786085074717 - #89

Open
imMamdouhaboammar wants to merge 11 commits into
antonbabenko:masterfrom
imMamdouhaboammar:ecc-tools/agent-plugins-1786085074717
Open

Ecc tools/agent plugins 1786085074717#89
imMamdouhaboammar wants to merge 11 commits into
antonbabenko:masterfrom
imMamdouhaboammar:ecc-tools/agent-plugins-1786085074717

Conversation

@imMamdouhaboammar

Copy link
Copy Markdown

Pull Request

Description

Plugin(s) affected:

Type of change:

  • New plugin
  • New content (best practices, patterns, guidance)
  • Fix (correcting outdated or incorrect information)
  • Refactor (reorganizing or improving clarity)
  • Documentation (README, CONTRIBUTING, CLAUDE.md)
  • CI / tooling

Summary:

Conventional Commit

Releases are per-plugin and driven by the commit scope. The squash/merge
commit subject must be scoped to the plugin:

  • feat(<plugin>): ... -> minor bump for that plugin
  • fix(<plugin>): ... -> patch bump
  • feat(<plugin>)!: ... or BREAKING CHANGE: in body -> major bump
  • No plugin scope -> no release

Planned commit subject: ____(________): ________________

Testing Evidence (REQUIRED for content changes)

Baseline Behavior (WITHOUT changes)

Prompt: [test prompt]
Agent response: [verbatim or screenshot]
Issues: [what was missing or incorrect]

Behavior (WITH changes)

Prompt: [same test prompt]
Agent response: [verbatim or screenshot]
Improvements: [what improved / patterns now followed]
  • Ran the plugin's tests/baseline-scenarios.md per its
    ## Running These Tests (plugin OFF then ON)
  • Every scenario meets its ### Success Criteria; no scenario fails
  • Added/updated a scenario for any new or changed behavior
  • Agent references new content
  • Agent applies new patterns proactively
  • No new rationalizations introduced

Standards Compliance Checklist

Frontmatter (if SKILL.md changed)

  • name and description present; name is letters/numbers/hyphens only
  • Description starts with "Use when..." and is < 1024 chars
  • metadata.version (if present) matches the manifest plugin version
    (or left for CI; do not hand-bump)

Token Efficiency & Content Quality

  • SKILL.md remains lean (target <500 lines)
  • Detailed content lives in references/*.md
  • Tables over prose; imperative voice; DO vs DON'T where useful
  • Code examples complete and runnable
  • LLM Consumption Rules in CLAUDE.md followed

Marketplace / Structure

External plugin (referenced repo):

  • plugins[] entry with source: { source: github, repo: owner/repo, ref: vX.Y.Z }
  • No local content / CHANGELOG / scoped-commit release
  • version (if set) is a manual mirror of source.ref

Inline plugin (content here):

  • plugins[] entry with source: ./plugins/<plugin>
  • plugins/<plugin>/skills/<plugin>/SKILL.md exists
  • plugins/<plugin>/CHANGELOG.md exists
  • No version numbers hand-edited (CI owns them)

Validation

  • Frontmatter validation passes
  • Manifest <-> SKILL.md version sync passes
  • No broken internal links
  • Markdown lint clean

Related Issues

Closes #
Relates to #


For Maintainers

  • Testing evidence convincing (baseline -> improved)
  • Standards compliance verified
  • Squash with a correctly scoped conventional commit subject
  • Confirm the resulting per-plugin version bump is intended

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