agentsclimarketplace
Sign in

Ccctx update

Skill mauromedda/ccctx/skills/ccctx-update

Update ccctx dependencies, Go version metadata, CI, documentation, GitHub templates, plugin metadata, and project maintenance files while preserving behavior. Use when asked to modernize, refresh, upgrade, document, prepare a release, or keep this repository current.From its SKILL.md

Install
npx -y skills add mauromedda/ccctx --skill ccctx-update

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 390 tokens by cl100k_base, as published. Nobody here has run it

ccctx Update

Keep maintenance changes boring, explicit, and verified.

Context To Read

  • go.mod
  • README.md
  • CONTRIBUTING.md
  • docs/architecture.md
  • docs/development.md
  • .github/workflows/ci.yml when present
  • .claude-plugin/plugin.json and skills/*/SKILL.md when skills or Claude Code support are in scope

Workflow

  1. Identify the requested maintenance surface: Go version, docs, CI, skills, GitHub metadata, release notes, or all of them.
  2. Preserve the cmd/ccctx plus internal/ccctx layout unless the user explicitly asks for a larger restructure.
  3. Keep the project dependency-light. Do not add third-party Go modules unless they remove real complexity.
  4. Update docs in the same change when commands, paths, environment variables, installation, or workflows change.
  5. Run gofmt on changed Go files.
  6. Run go test ./..., go vet ./..., and go build -o bin/ccctx ./cmd/ccctx.
  7. If plugin or skills changed and claude is available, run claude plugin validate . --strict.

Guardrails

  • The project is MIT licensed; preserve LICENSE unless the maintainer explicitly changes licensing.
  • Do not commit generated binaries, profile snapshots, Claude configs, credentials, or tokens.
  • Keep examples safe by using temporary directories and fake Claude config paths.
  • Keep README user-focused; put contributor detail in CONTRIBUTING.md and docs/.
  • Keep llms.txt concise and accurate after layout changes.

Done Criteria

  • Maintenance files are internally consistent.
  • Commands in docs work from a fresh checkout.
  • CI mirrors local checks.
  • The final response names the checks run and any checks skipped.

What ships with it: 1 file

181 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,452. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.