jj-vcs/jj

1 other commands the scanner could not classify

Commands from CI steps and task runners that look like checks but match no known tool. Some are checks, some are not.

• nix flake check -L --show-trace

full scan as JSON

• consistent command flag designDesign command-line interfaces with consistent flag semantics and leverage framework features for validation. Avoid ambiguous syntax that...

  jj-vcs/jj API Rust devtools 2025-10-15

  copy raw open
• Define technical terms clearlyAlways define technical terms and concepts explicitly in documentation rather than assuming reader knowledge. Avoid ambiguous phrasing th...

  jj-vcs/jj Documentation Markdown devtools 2025-10-11

  copy raw open
• eliminate redundant codeRemove unnecessary code, operations, and annotations that don't add value. This includes redundant type annotations when types are alread...

  jj-vcs/jj Code Style Rust devtools 2025-10-10

  copy raw open
• prioritize documentation clarityWrite documentation that prioritizes user understanding over technical precision. Avoid unclear phrases, overly technical explanations, a...

  jj-vcs/jj Documentation Rust devtools 2025-10-14

  copy raw open
• Choose efficient data structuresSelect data structures and algorithms based on their performance characteristics and expected usage patterns. Consider the size of collec...

  jj-vcs/jj Algorithms Rust devtools 2025-10-15

  copy raw open
• Use type-specific variable namesUse distinct variable names that reflect their types to avoid confusion and make code intent clearer. Avoid reusing the same variable nam...

  jj-vcs/jj Naming Conventions Rust devtools 2025-10-18

  copy raw open
• Consistent naming conventionsMaintain consistent naming and terminology throughout code and documentation. This includes proper capitalization of product names, techn...

  jj-vcs/jj Naming Conventions Markdown devtools 2025-10-12

  copy raw open
• Minimize API scopeWhen designing APIs, prioritize simplicity and focused scope over feature completeness. Before adding new API methods or expanding existi...

  jj-vcs/jj API Markdown devtools 2025-09-11

  copy raw open
• preserve error contextWhen handling errors, preserve the original error context and avoid exposing internal representations to users. Use `IoResultExt::context...

  jj-vcs/jj Error Handling Rust devtools 2025-09-11

  copy raw open
• Use safe optional defaultsWhen working with optional values, prefer safe extraction methods that provide defaults rather than methods that can panic. Use `unwrap_o...

  jj-vcs/jj Null Handling Rust devtools 2025-10-17

  copy raw open
• Config file naming clarityUse descriptive, unambiguous names for configuration files to clearly indicate their scope and prevent user confusion about configuration...

  jj-vcs/jj Configurations Rust devtools 2025-10-10

  copy raw open
• Use intuitive descriptive namesChoose names that clearly communicate purpose and intent without requiring additional documentation or context. Names should be self-expl...

  jj-vcs/jj Naming Conventions Other devtools 2025-09-23

  copy raw open
• documentation formatting consistencyMaintain consistent formatting and style patterns across all documentation to improve readability and user experience. This includes usin...

  jj-vcs/jj Code Style Markdown devtools 2025-09-03

  copy raw open
• optimize remote fetch operationsWhen implementing network operations that fetch data from remote sources, configure specific refspecs or patterns to fetch only the requi...

  jj-vcs/jj Networking Rust devtools 2025-10-11

  copy raw open
• Verify test assertionsAlways use appropriate assertion methods in tests to ensure proper verification of command behavior. When you don't need to examine comma...

  jj-vcs/jj Testing Rust devtools 2025-10-03

  copy raw open
• precise algorithmic terminologyWhen documenting or describing algorithmic operations, use precise, unambiguous terminology that clearly distinguishes between different ...

  jj-vcs/jj Algorithms Markdown devtools 2025-10-01

  copy raw open
• document test configurationsWhen modifying test configurations or tooling settings, provide clear explanations of what the changes actually do and why specific optio...

  jj-vcs/jj Testing Toml devtools 2025-09-24

  copy raw open
• ensure cross-platform compatibilityWhen creating configuration files and build tasks, prioritize cross-platform compatibility by avoiding shell-specific syntax and consider...

  jj-vcs/jj Configurations Toml devtools 2025-09-14

  copy raw open
• Multiple remote configurationWhen documenting or implementing features that involve multiple remote repositories, provide clear guidance on different remote configura...

  jj-vcs/jj Networking Markdown devtools 2025-09-08

  copy raw open
• specify configuration scopeAlways explicitly specify the configuration scope using `--user` or `--repo` flags when setting configuration values with `jj config set`...

  jj-vcs/jj Configurations Markdown devtools 2025-09-07

  copy raw open
• require explicit security consentAlways require explicit user consent and validation before executing potentially dangerous operations, especially those involving externa...

  jj-vcs/jj Security Rust devtools 2025-09-02

  copy raw open
• GitHub Actions security reviewAlways review GitHub Actions workflows for security implications before merging, particularly focusing on authentication mechanisms and c...

  jj-vcs/jj Security Yaml devtools 2025-08-22

  copy raw open
• Pin actions to commitsUse specific commit hashes instead of version tags when referencing GitHub Actions in CI/CD workflows. Version tags can be moved or updat...

  jj-vcs/jj CI/CD Yaml devtools 2025-08-22

  copy raw open