There's a potential nil pointer dereference here. os.Stat(srcPath) can return an error other than os.IsNotExist. In that case, the error is not handled, and execution continues. Later, on line 130, info.IsDir() would cause a panic because info would be nil. You should handle all non-nil errors from os.Stat.

    info, err := os.Stat(srcPath)
    if err != nil {
        if os.IsNotExist(err) {
            if c.verbose {
                fmt.Printf("Shared resource source not found: %s\n", srcPath)
            }
            return nil // Not an error, just nothing to sync
        }
        return fmt.Errorf("failed to stat source resource %s: %w", srcPath, err)
    }

The error returned by c.GetWorktreeRoot() is ignored. If this call fails, root will be an empty string. This will cause strings.HasPrefix(cwd, root) on line 183 to always evaluate to true, leading to incorrect path manipulation logic later on. You should handle this error to prevent unexpected behavior.

    root, err := c.GetWorktreeRoot()
    if err != nil {
        fmt.Printf("Error: could not determine project root: %v\n", err)
        return
    }

The logic for selecting a strategy interactively is also present in promptAddResource (lines 208-220). To avoid duplication and improve maintainability, you could extract this logic into a helper function, for example: func promptForStrategy(reader *bufio.Reader) worktree.ResourceStrategy. This would centralize the prompt text and input parsing.

The error from reader.ReadString('\n') is ignored. If an error occurs (e.g., io.EOF if the user presses Ctrl+D), the program will continue with a potentially empty or partial strategyStr, leading to incorrect behavior. This pattern of ignoring errors from ReadString is repeated throughout the file (e.g., lines 154, 196, 212, 228, 241). It's best practice to handle these errors.

            strategyStr, err := reader.ReadString('\n')
            if err != nil {
                return fmt.Errorf("failed to read strategy input: %w", err)
            }

The test hardcodes the expected symlink target as "../models". This will fail on Windows, where the path separator is \ and the relative path would be ..\models. To make this test platform-independent, you should use a helper from the path/filepath package to construct the expected path.

The warning message is printed to standard output using fmt.Printf. It's conventional for warnings and errors to be printed to standard error (stderr). This allows users to redirect normal output (stdout) without losing visibility of warnings. You should use fmt.Fprintf(os.Stderr, ...) instead.

The warning message is printed to standard output using fmt.Printf. It's conventional for warnings and errors to be printed to standard error (stderr). This allows users to redirect normal output (stdout) without losing visibility of warnings. You should use fmt.Fprintf(os.Stderr, ...) instead.