Skip to content

Lead the README and listing with "Works in Claude Code" - #11

Merged
Rmasood1122 merged 3 commits into
mainfrom
docs/works-in-claude-code
Oct 20, 2026
Merged

Rmasood1122 merged 3 commits into
mainfrom
docs/works-in-claude-code

Conversation

@Rmasood1122

Copy link
Copy Markdown
Owner

Summary

The plugin runs in Claude Code, so the README and the listing now say that first, followed by the two commands that install it there.

Before After
README line 1 # CommitProof (the title) Works in Claude Code. To install, run these two commands in a Claude Code session: then the install block, then the title
Install block further down the README /plugin marketplace add Rmasood1122/commitproof
/plugin install commitproof@commitproof
plugin.json + marketplace.json descriptions start with the problem start with Works in Claude Code., rest unchanged
Listing checks none in this repo new tests/test_listing_readiness.py: kebab-case name, description 30–2000 chars, non-empty keywords, marketplace lists exactly this plugin

Evidence

  • New tests/test_install_routing.py: README line 1, the install block right after it, the description lead, and every README install command pointing at this repo's own marketplace by the manifest names. Red before the change, green after.
  • New tests/test_listing_readiness.py: the directory's manifest checks; green before and after, and each check fails when its field is broken.
  • Full suite: 113 → 120 passed (python -m pytest tests/ -q).
  • claude plugin validate --strict . and claude plugin validate --strict .claude-plugin/plugin.json: both exit 0.
  • Live check: in a fresh, logged-out Claude Code 2.1.299 config, the two README commands (CLI form) install the plugin and claude plugin list shows it enabled.

Merge danger

Door: two-way (README and description text; a revert undoes it). Blast radius: listing. Once merged, the claude.ai directory picks up the new description on its next check of this branch.

🤖 Generated with Claude Code

Rmasood1122 and others added 3 commits October 20, 2026 18:32
This plugin runs in Claude Code. The README now opens with that fact and
the two commands that install it there, and the plugin and marketplace
descriptions both start with "Works in Claude Code".

tests/test_install_routing.py pins it: README line 1, the install block right
after it, the description lead, and every README install command pointing at
this repo's own marketplace by the names the manifests declare.

tests/test_listing_readiness.py adds the directory's manifest checks this repo
lacked: kebab-case name, description 30-2000 characters, non-empty keywords,
and a marketplace that lists exactly this plugin.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uditors ask for

No SOC 2, HIPAA or PCI control requires AI-code provenance, so the README
line "the change-control evidence a SOC 2, HIPAA or PCI auditor asks for"
and the listing's "change-control evidence for SOC 2, HIPAA or PCI audits"
claimed more than the report can back. Both now say it is a report you can
give an auditor as supporting evidence, matching what /receipt-report and
the receipt-integrity skill already tell users.

test_listing_readiness.py fails on "auditor asks for"-style wording and on a
SOC 2 mention without the supporting-evidence framing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The test only matched owner/repo slugs and name@marketplace pairs, so a
URL-form `marketplace add https://github.com/...` or a bare `plugin install
name` would slip past it. It now compares whole tokens, and an unclosed
install block fails with a message instead of a bare StopIteration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Rmasood1122
Rmasood1122 merged commit e745f5e into main Oct 20, 2026
4 checks passed
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