### Install resume-cli Source: https://github.com/jsonresume/resume-cli/blob/master/README.md Install the command-line tool globally using npm. This command is required before using any resume-cli functionalities. ```bash npm install -g resume-cli ``` -------------------------------- ### Serve Resume Locally Source: https://github.com/jsonresume/resume-cli/blob/master/README.md Starts a local web server to display your resume. It supports live reloading when changes are made to your resume.json. This is useful for theme development or previewing changes. ```bash resume serve --port --theme ``` -------------------------------- ### Scope Example Source: https://github.com/jsonresume/resume-cli/blob/master/CONTRIBUTING.md Provide an optional scope in parentheses after the commit type to add contextual information, such as specifying a feature related to theming. ```txt feat(theme): add ability to specify theme ``` -------------------------------- ### Export Resume to HTML or PDF Source: https://github.com/jsonresume/resume-cli/blob/master/README.md Exports your resume data into a stylized HTML or PDF format. Ensure you have installed the desired theme using npm before exporting. You can specify the output format and theme. ```bash resume export [fileName] --format Example: --format pdf --theme Example: --theme even ``` -------------------------------- ### Commit Type Examples Source: https://github.com/jsonresume/resume-cli/blob/master/CONTRIBUTING.md Use specific types for commit messages: 'fix' for bug fixes (PATCH release), 'feat' for new features (MINOR release). Other types like 'build', 'docs', 'refactor', 'test' are also recommended. ```txt fix: for a bug fix (corresponds to a PATCH release); feat: for a new feature (corresponds to a MINOR release); other non-release types such as build:, docs:, refactor:, test: and others (see recommended) ``` -------------------------------- ### Resume CLI Commands Overview Source: https://github.com/jsonresume/resume-cli/blob/master/README.md A quick reference for the available commands in the resume-cli tool. Each command serves a specific purpose in managing your JSON Resume. ```bash init validate export path/to/file.html serve ``` -------------------------------- ### Serve Local Theme Directory Source: https://github.com/jsonresume/resume-cli/blob/master/README.md When developing themes, navigate to your theme directory and run this command. It tells resume-cli to serve the current directory as the theme. ```bash resume serve --theme . ``` -------------------------------- ### Description Guidelines Source: https://github.com/jsonresume/resume-cli/blob/master/CONTRIBUTING.md When writing the description, use the imperative present tense, do not capitalize the first letter, and do not end with a period. ```txt use the imperative, present tense, e.g. "change", not "changed" nor "changes"; don't capitalize the first letter; no period (.) at the end. ``` -------------------------------- ### Run Development Script Source: https://github.com/jsonresume/resume-cli/blob/master/CONTRIBUTING.md Execute the development script for the CLI application. Any CLI arguments can be passed after the double-dash separator. ```sh npm run dev -- [cli arguments can be passed after the double-dash] ``` -------------------------------- ### Reading Resume Data from a File Path Source: https://github.com/jsonresume/resume-cli/blob/master/README.md Specifies a file path from which the CLI should read resume data. If this option is omitted, the CLI defaults to reading from 'resume.json' in the current working directory. ```bash --resume ``` -------------------------------- ### Reading Resume Data from Standard Input Source: https://github.com/jsonresume/resume-cli/blob/master/README.md Instructs the CLI to read resume data from standard input (STDIN). The default MIME type for STDIN is 'application/json'. ```bash --resume - ``` -------------------------------- ### Conventional Commit Message Structure Source: https://github.com/jsonresume/resume-cli/blob/master/CONTRIBUTING.md Follow this structure for commit messages to ensure automated versioning and release notes. The type indicates the nature of the change, and an optional scope provides context. ```txt [optional scope]: ``` -------------------------------- ### Breaking Change Indicator Source: https://github.com/jsonresume/resume-cli/blob/master/CONTRIBUTING.md Append an exclamation mark '!' after the type or scope to indicate a breaking change, which corresponds to a MAJOR release. ```txt type!: breaking change ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.