Skill: New pull request for TheAlgorithms/Python (#15212)

* Skill: New pull request for TheAlgorithms/Python

@priya-sundaram-dev, please review and suggest any changes.  We want to make sure that the keeper does not close new PRs as invalid.

* updating DIRECTORY.md

* Update pull request instructions in SKILL.md

Clarified instructions for creating a new pull request and emphasized the importance of branch naming.

* Clarify Markdown checkbox requirement for PRs

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Skill: fix uv.lock wording; add DIRECTORY.md/README.md auto-gen note (#15216)

- Clarify that uv.lock is regenerated by the uv-lock pre-commit hook when a
  legitimate dependency is added; only hand-edits/reverts break the keeper.
- Add a checklist item: DIRECTORY.md and README.md are bot-generated, don't
  hand-edit them.

---------

Co-authored-by: cclauss <cclauss@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: priya-sundaram-dev <oc-409d01@agentmail.to>

Author: 3 people

.github/skills/new-pull-request/SKILL.md

@@ -0,0 +1,52 @@
+# Skill: New pull request for TheAlgorithms/Python
+
+Create a new pull request using the rules already written in
+[`CONTRIBUTING.md`](../../../CONTRIBUTING.md). The goal is that creating a new
+pull request (human or AI) can run the same way every time, and that produces a
+clear, kind, tested, type-hinted, mergeable contribution.
+
+## How to run this skill
+
+Make sure that the local `master` branch is synced with `upstream/master` before
+creating a new pull request.
+
+Create a new clearly named branch for the pull request.  Pull request changes must
+not be made or submitted on the `master` branch.
+
+Never hand-edit or revert the `uv.lock` file. If you add a legitimate
+dependency, let the `uv-lock` pre-commit hook regenerate it — do not touch it by
+hand. A hand-modified `uv.lock` makes the `algorithms-keeper` bot close the pull
+request as invalid, and even a repo maintainer cannot undo that.
+
+Always check at least one Markdown checkbox in the pull request description (the "Describe your change" section), or the
+`algorithms-keeper` bot will close the pull request as invalid.  Any repo maintainer can undo this if you @mention them on the closed pull request.
+
+### 1. Before contributing / Is this an algorithm?
+
+- [ ] The change adds, fixes, or documents **one algorithm** — not multiple, and
+      not both code and doctest changes in the same PR.
+- [ ] It is a genuine algorithm or data structure (see the *What is an Algorithm?*
+      section), not a script, snippet, how-to-use for an existing API, or exercise
+      dump.
+- [ ] It is **not already in the repository** (search the existing directories).
+- [ ] **No earlier open PR** already does the same thing — link it if one exists.
+- [ ] Properly attributed — no plagiarism; prior sources credited.
+
+### 2. Coding Style
+
+- [ ] `from __future__ import annotations` is not needed because this repo only uses
+      the latest version of CPython.
+- [ ] File and directory names are lowercase, use underscores, and land inside an
+      existing directory.
+- [ ] Public functions/classes have **type hints**.
+- [ ] Public functions have **doctests that actually pass**.
+- [ ] Descriptive variable and function names (no single letters where a word helps).
+- [ ] Code is formatted and lint-clean (`ruff`, `pre-commit`).
+- [ ] `DIRECTORY.md` and `README.md` are **not hand-edited** — the
+      `algorithms-keeper` bot regenerates them automatically after merge.
+
+### 3. Other Requirements for Submissions
+
+- [ ] At least one **Wikipedia (or equivalent) URL** documenting the algorithm.
+- [ ] Docstring explains what the function does and its parameters/returns.
+- [ ] No unnecessary third-party dependencies.

DIRECTORY.md

@@ -669,7 +669,9 @@
   * Forecasting
     * [Run](machine_learning/forecasting/run.py)
   * [Frequent Pattern Growth](machine_learning/frequent_pattern_growth.py)
+  * [Gaussian Naive Bayes](machine_learning/gaussian_naive_bayes.py)
   * [Gradient Boosting Classifier](machine_learning/gradient_boosting_classifier.py)
+  * [Gradient Boosting Regressor](machine_learning/gradient_boosting_regressor.py)
   * [Gradient Descent](machine_learning/gradient_descent.py)
   * [K Means Clust](machine_learning/k_means_clust.py)
   * [K Nearest Neighbours](machine_learning/k_nearest_neighbours.py)
@@ -685,6 +687,8 @@
   * [Multilayer Perceptron Classifier](machine_learning/multilayer_perceptron_classifier.py)
   * [Polynomial Regression](machine_learning/polynomial_regression.py)
   * [Principle Component Analysis](machine_learning/principle_component_analysis.py)
+  * [Random Forest Classifier](machine_learning/random_forest_classifier.py)
+  * [Random Forest Regressor](machine_learning/random_forest_regressor.py)
   * [Scoring Functions](machine_learning/scoring_functions.py)
   * [Self Organizing Map](machine_learning/self_organizing_map.py)
   * [Sequential Minimum Optimization](machine_learning/sequential_minimum_optimization.py)
@@ -923,6 +927,7 @@
   * [Back Propagation Neural Network](neural_network/back_propagation_neural_network.py)
   * [Convolution Neural Network](neural_network/convolution_neural_network.py)
   * [Input Data](neural_network/input_data.py)
+  * [Perceptron](neural_network/perceptron.py)
   * [Simple Neural Network](neural_network/simple_neural_network.py)
   * [Two Hidden Layers Neural Network](neural_network/two_hidden_layers_neural_network.py)
 
@@ -975,6 +980,7 @@
   * [Lorentz Transformation Four Vector](physics/lorentz_transformation_four_vector.py)
   * [Malus Law](physics/malus_law.py)
   * [Mass Energy Equivalence](physics/mass_energy_equivalence.py)
+  * [Maxwells Equations](physics/maxwells_equations.py)
   * [Mirror Formulae](physics/mirror_formulae.py)
   * [N Body Simulation](physics/n_body_simulation.py)
   * [Newtons Law Of Gravitation](physics/newtons_law_of_gravitation.py)