Add missing page + Some more tweaks

Author: ZakaHaceCosas

.vscode/settings.json

@@ -22,6 +22,7 @@
         "fkstart",
         "fkstats",
         "fksurrender",
+        "fkuncommit",
         "fontawesome",
         "framagit",
         "fuckingnode",

docs/about/why.md

@@ -16,7 +16,7 @@ _And the list goes on..._
 
 ## What we fixed, and how
 
-I initially created FuckingNode as a `.ps1` script to automate `npm prune` and `pnpm store prune` across a fixed list of personal projects, and as you can see, it has grown into four major releases, eleven separate utilities (`clean`, `kickstart`, `release`, `commit`, `surrender`, `setup`, `stats`, `launch`, `build`, `migrate`, `audit`), DenoJS & BunJS support, and even a small amount of features bridged to Go and Cargo.
+I initially created FuckingNode as a `.ps1` script to automate `npm prune` and `pnpm store prune` across a fixed list of personal projects, and as you can see, it has grown into five major releases, thirteen separate utilities (`clean`, `kickstart`, `release`, `commit`, `uncommit`, `surrender`, `setup`, `stats`, `launch`, `build`, `migrate`, `audit`, `terminate`), DenoJS & BunJS support, and even a small amount of features bridged to Go and Cargo.
 
 FuckingNode exists because it fixes all of the issues mentioned above.
 

docs/index.html

@@ -542,12 +542,8 @@ <h2>
           </h2>
         </div>
         <p>
-          <b style="color: #000; padding: 5px; background-color: #ffc832"
-          >WEBSITE UNDER CONSTRUCTION! we're updating the documentation for
-            FuckingNode 5, which should come out today. docs don't reflect the
-            current CLI!</b>
-          <!-- FuckingNode is a unique, state of the art CLI to automate headache
-          giving tasks and make it easier to develop in N*deJS, Deno, or Bun. -->
+          FuckingNode is a unique, state of the art CLI to automate headache
+          giving tasks and make it easier to develop in N*deJS, Deno, or Bun.
         </p>
         <div class="buttons">
           <a href="manual/" class="btn">Get started!</a>
@@ -557,7 +553,10 @@ <h2>
         </div>
       </div>
       <div class="hero-visual">
-        <img src="https://fuckingnode.github.io/hero.webp" alt="FuckingNode doing some cleanup">
+        <img
+          src="https://fuckingnode.github.io/hero.webp"
+          alt="FuckingNode doing some cleanup"
+        >
       </div>
     </section>
 
@@ -657,6 +656,8 @@ <h2>You spend a bit too much time messing with config files</h2>
       </div>
     </section>
 
+    <p style="text-align: center;">There's actually a lot more features, find out by looking at our docs.</p>
+
     <section id="faq">
       <h3>FAQ</h3>
       <p class="section-desc">

docs/install.ps1

@@ -68,6 +68,7 @@ Function New-Shortcuts {
             "fkstart"     = "kickstart"
             "fklaunch"    = "launch"
             "fkcommit"    = "commit"
+            "fkuncommit"  = "uncommit"
             "fkbuild"     = "build"
             "fkrelease"   = "release"
             "fksurrender" = "surrender"

docs/install.sh

@@ -106,6 +106,7 @@ create_shortcuts() {
         ["fkstart"]="kickstart"
         ["fklaunch"]="launch"
         ["fkcommit"]="commit"
+        ["fkuncommit"]="uncommit"
         ["fkbuild"]="build"
         ["fkrelease"]="release"
         ["fksurrender"]="surrender"

docs/manual/commit.md

@@ -55,4 +55,4 @@ You can also run the command with the `--yes` flag to skip this - though we don'
 
 You've now learnt how to speed up commits.
 
-Next: Release - How to speed up npm / jsr package releases?
+Next: Uncommit - How to speed up fixing fucked up commits?

docs/manual/uncommit.md

@@ -0,0 +1,50 @@
+---
+title: "FuckingNode Uncommitter"
+description: "Made a fucked up commit? Easily undo it."
+---
+
+# Using FuckingNode: Unmake a commit
+
+> `fuckingnode uncommit`, or `fkuncommit`
+
+The `uncommit` command in FuckingNode allows you to quickly remake a commit. It automatically undoes the last local commit (storing its name), then hangs for you to modify its files as needed, and once you tell it to run, it re-runs `commit` (including `commitCmd` if any) and remakes the commit with the same message.
+
+## Usage
+
+To uncommit changes to your project, just run this from the root of the repo:
+
+```bash
+fuckingnode uncommit
+```
+
+### What to expect
+
+You'll see a confirmation like this one, showing what will be made:
+
+```txt
+❓ We will unstage all currently staged files (if any), and immediately undo commit 39a6d31.
+If you terminate the program you won't recover it, it's us who handle remaking it. Proceed?
+Confirm? [y/N]
+```
+
+If you input `y`, the commit will be unmade and you'll see this:
+
+```txt
+Undid commit 39a6d31 (some wrong commit, by ZakaHaceCosas at Sun Sep 28 15:30:47 2025 +0200)
+
+Make any modifications to the existing files now.
+Use regular git commands (git add / git remove) from a separate terminal to stage/unstage files.
+Once done, come to this terminal and hit 'Y',
+    we'll run your commitCmd (if any) and re-make the commit with the same message and files (unless changed) as before.
+You may hit 'n' as well, result will be the same.
+
+waiting for you to hit 'Y' [y/N] 
+```
+
+After hitting `y` (or `n`), our [commit command](commit.md) will immediately run and your commit will be remade (unless a `commitCmd` exists and fails, of course).
+
+---
+
+You've now learnt how to speed up fixing fucked up commits.
+
+Next: Release - How to speed up npm / jsr package releases?

mkdocs.yml

@@ -22,6 +22,7 @@ nav:
           - Individual project configuration: "manual/fknode-yaml.md"
           - Feature - Kickstart: "manual/kickstart.md"
           - Feature - Commit: "manual/commit.md"
+          - Feature - Uncommit: "manual/uncommit.md"
           - Feature - Build: "manual/build.md"
           - Feature - Release: "manual/release.md"
           - Feature - Launch: "manual/launch.md"