Available Options
Specify a custom configuration file path.Default: Use this when:
.linkspector.ymlExample:- You have multiple environments (dev, staging, production)
- Your config file is in a non-standard location
- You want to test different configurations without modifying your main config
Output the results in JSON format (Reviewdog Diagnostic Format).Default: The JSON output follows the Reviewdog Diagnostic Format (RDJSON) specification, making it easy to integrate with CI/CD pipelines and code review tools.Note: Cannot be used with
falseExample:--showstat.Example output structure:Display detailed statistics about the links checked.Default: Shows a formatted table with:
falseExample:- Total files checked
- Total links checked
- Breakdown by link type (HTTP, file, email)
- Count of working vs failed links
--json.Example output:Option Combinations
Valid Combinations
You can combine compatible options:Incompatible Options
The--json and --showstat options cannot be used together. If you try to combine them, Linkspector will exit with an error:
--jsonis for machine-readable output (CI/CD integration)--showstatis for human-readable statistics (local development)
When to Use Each Option
Use --config when:
- Working with multiple projects or environments
- Testing different configuration settings
- Your configuration file is not in the default location
- Running Linkspector from a different directory
Use --json when:
- Integrating with CI/CD pipelines
- Parsing results programmatically
- Using with code review tools like Reviewdog
- Generating reports in other formats
- Need precise location information for errors
Use --showstat when:
- Running checks locally during development
- Want to see overall health of your documentation
- Need to understand the distribution of link types
- Monitoring link quality over time
- Generating summary reports for stakeholders