{
    "mode": "man",
    "parameter": "BUNDLE-GEM",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/man/BUNDLE-GEM/json",
    "generated": "2026-10-22T12:35:07Z",
    "synopsis": "bundle gem GEMNAME OPTIONS",
    "sections": {
        "NAME": {
            "content": "bundle-gem - Generate a project skeleton for creating a rubygem\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "bundle gem GEMNAME OPTIONS\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "Generates  a directory named GEMNAME with a Rakefile, GEMNAME.gemspec, and other supporting\nfiles and directories that can be used to develop a rubygem with that name.\n\nRun rake -T in the resulting project for a list of Rake tasks that can be used  to  test  and\npublish the gem to rubygems.org.\n\nThe  generated project skeleton can be customized with OPTIONS, as explained below. Note that\nthese options can also be specified via Bundler´s global configuration file using the follow‐\ning names:\n\n•   gem.coc\n\n•   gem.mit\n\n•   gem.test\n\n\n",
            "subsections": []
        },
        "OPTIONS": {
            "content": "•   --exe or -b or --bin:  Specify  that  Bundler  should  create  a  binary  executable  (as\nexe/GEMNAME)  in  the  generated  rubygem project. This binary will also be added to the\nGEMNAME.gemspec manifest. This behavior is disabled by default.\n\n•   --no-exe: Do not create a binary (overrides --exe specified in the global config).\n\n•   --coc: Add a CODEOFCONDUCT.md file to the root of the generated project. If this option\nis unspecified, an interactive prompt will be displayed and the answer will be  saved  in\nBundler´s global config for future bundle gem use.\n\n•   --no-coc:  Do  not  create  a CODEOFCONDUCT.md (overrides --coc specified in the global\nconfig).\n\n•   --ext=c, --ext=rust Add boilerplate for C or Rust (currently magnus  https://docs.rs/mag‐\nnus based) extension code to the generated project. This behavior is disabled by default.\n\n•   --no-ext: Do not add extension code (overrides --ext specified in the global config).\n\n•   --mit:  Add  an  MIT  license to a LICENSE.txt file in the root of the generated project.\nYour name from the global git config is used for the copyright statement. If this  option\nis  unspecified,  an interactive prompt will be displayed and the answer will be saved in\nBundler´s global config for future bundle gem use.\n\n•   --no-mit: Do not create a LICENSE.txt (overrides --mit specified in the global config).\n\n•   -t, --test=minitest, --test=rspec, --test=test-unit:  Specify  the  test  framework  that\nBundler should use when generating the project. Acceptable values are minitest, rspec and\ntest-unit.  The  GEMNAME.gemspec  will  be configured and a skeleton test/spec directory\nwill be created based on this option. Given no option is specified:\n\nWhen Bundler is configured to generate tests, this defaults to  Bundler´s  global  config\nsetting gem.test.\n\nWhen Bundler is configured to not generate tests, an interactive prompt will be displayed\nand the answer will be used for the current rubygem project.\n\nWhen Bundler is unconfigured, an interactive prompt will be displayed and the answer will\nbe saved in Bundler´s global config for future bundle gem use.\n\n•   --ci,  --ci=github,  --ci=gitlab, --ci=circle: Specify the continuous integration service\nthat Bundler should use when generating the project. Acceptable values are github, gitlab\nand circle. A configuration file will be generated in the project directory. Given no op‐\ntion is specified:\n\nWhen Bundler is configured to generate CI files, this defaults to Bundler´s global config\nsetting gem.ci.\n\nWhen Bundler is configured to not generate CI files, an interactive prompt will  be  dis‐\nplayed and the answer will be used for the current rubygem project.\n\nWhen Bundler is unconfigured, an interactive prompt will be displayed and the answer will\nbe saved in Bundler´s global config for future bundle gem use.\n\n•   --linter, --linter=rubocop, --linter=standard: Specify the linter and code formatter that\nBundler should add to the project´s development dependencies. Acceptable values are rubo‐\ncop  and standard. A configuration file will be generated in the project directory. Given\nno option is specified:\n\nWhen Bundler is configured to add a linter, this defaults to Bundler´s global config set‐\nting gem.linter.\n\nWhen Bundler is configured not to add a linter, an interactive prompt will  be  displayed\nand the answer will be used for the current rubygem project.\n\nWhen Bundler is unconfigured, an interactive prompt will be displayed and the answer will\nbe saved in Bundler´s global config for future bundle gem use.\n\n•   -e, --edit[=EDITOR]: Open the resulting GEMNAME.gemspec in EDITOR, or the default editor\nif not specified. The default is $BUNDLEREDITOR, $VISUAL, or $EDITOR.\n\n\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "•   bundle config(1) bundle-config.1.html\n\n\n\n\nAugust 2023                               BUNDLE-GEM(1)",
            "subsections": []
        }
    },
    "summary": "bundle-gem - Generate a project skeleton for creating a rubygem",
    "flags": [],
    "examples": [],
    "see_also": [
        {
            "name": "config",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/config/1/json"
        }
    ]
}