project-licenselisted

# Create Project License Select, generate, and apply the correct LICENSE file for a repository based on its namespace and ownership. ## Workflow 1. **Detect Ownership & Organization**: Inspect git remotes (`git remote -v`), configuration files (`pyproject.toml`, `go.mod`, etc.), or directory naming to determine the repository's target GitHub organization or user namespace. 1. **Select License Standard**: - If the project is associated with the GitHub organizations or users **`fmind`** or **`fmind-ai`** (e.g., `github.com/fmind/...`, `github.com/fmind-ai/...`) and is public, use the **MIT License**. - Otherwise, the project is **Proprietary** and must NOT use an open-source license. 1. **Generate LICENSE File**: - Write the resolved license content to a `LICENSE` file at the root of the project. - Use the correct copyright holder name **"Médéric Hurier (Fmind)"** and the current year (e.g., `2026`). 1. **Update Configuration Files**: For Python, set the PEP 639 SPDX `license` field in `pyproject.toml` — `license = "MIT"` for MIT or `license = "LicenseRef-Proprietary"` for proprietary (plain `"Proprietary"` is not a valid SPDX expression and modern build tools reject it) — and add `license-files = ["LICENSE"]`. Go modules have no license field in `go.mod`. ## License Templates To keep this skill light and maintainable, the license texts are stored as separate files: - **MIT License Template**: [MIT](templates/MIT) (for `fmind` and `fmind-ai` projects, resolvin