AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

open-sourcing

This skill should be used when the user asks to "open source this project", "prepare this repository for public release", "make this repo public", "check open-source readiness", "choose a license for this project", or "set up release automation" ahead of a public launch. Provides a release-readiness workflow covering secrets hygiene, licensing, documentation, CI, and language-specific packaging.

Original source
trailofbits
License
CC-BY-SA-4.0
Pinned revision
2be6433b39e009cd2b6fd3be1895f6b1faa5af9a

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read trailofbits--open-sourcing at revision 2be6433b39e009cd2b6fd3be1895f6b1faa5af9a, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 9

references/ruby.md

Ruby Release Practices

Supported versions

Ruby releases a minor version yearly and the community supports roughly the last three. Support those three; going lower buys little and costs CI matrix time. Declare the floor with required_ruby_version in the gemspec.

Dependencies

Use Bundler. Configure it to install into a vendor directory rather than the user's global gem store, and keep that directory out of git:

bundle config set --local path vendor/bundle
echo vendor/bundle/ >> .gitignore

Formatting and linting

Use RuboCop. The default cops are reasonable; projects commonly relax the metrics cops (method length, complexity) in .rubocop.yml rather than fighting them. Enforce in CI.

Publishing to RubyGems

  • Publish to RubyGems.org.
  • Use RubyGems trusted publishing from GitHub Actions instead of API keys.
  • Add the organization's shared account as a gem co-owner (gem owner <gem> --add <email>) so the package survives maintainer turnover.
  • Set spec.license (SPDX identifier) and spec.metadata links (source_code_uri, changelog_uri) in the gemspec.