DEV Community: Jack Scott

PS7-Completion: Tab completion for Git, SSH and WinGet in PowerShell

Jack Scott — Thu, 22 Oct 2026 22:20:34 +0000

The idea for PS7-Completion came from bash-completion. I wanted that same convenience in PowerShell: type part of a command, press Tab, and get some help with what comes next.

PowerShell already has tab completion, but the experience with command-line tools depends on which tool you’re using and what completion support you have installed. I wanted to make more of the commands I use feel familiar in that respect.

So I’m building PS7-Completion, an open-source module for PowerShell 7.4+ on Windows, with completion support for 34 tools.

Here’s what using it looks like.

You start typing a Git command:

git che

Press Tab, and it completes to:

git checkout

You can do the same with supported options. If you remember that Git has an option for a shorter log, start with:

git log --one

Tab completes it to:

git log --oneline

The WinGet equivalent might be an option you’ve used before but keep forgetting:

winget install --ex

Press Tab:

winget install --exact

You can continue typing from there. Pressing Tab fills in the suggestion; it doesn’t execute the command.

SSH completion also uses host aliases from your SSH config. If you have an alias called staging-web, typing this gives you a starting point:

ssh stag

Press Tab to complete the matching name:

ssh staging-web

It’s especially useful for tools you use just often enough to need them, but not often enough to remember their syntax. Opening the help output is fine. Opening it for the same option every few weeks gets old.

Alongside Git, SSH and WinGet, PS7-Completion covers tools including Docker, GitHub CLI, npm, pip, uv, Ruff, Cargo and ripgrep. The full list is in the README. Coverage varies between tools, and this is still an early release.

To try it, check that you’re running PowerShell 7.4 or newer:

$PSVersionTable.PSVersion

Download the Windows installer from the latest release page, run it, and open a new PowerShell session.

Then load the module:

Import-Module PS7-Completion

Try a few commands you normally use and press Tab while typing a subcommand or option.

If you decide to keep it, add that import line to your PowerShell profile so it loads in new sessions. The installer doesn’t edit your profile.

I’d appreciate feedback from people using it during ordinary terminal work. Pick a couple of tools you know well and see where the suggestions help or fall short.

If something is missing or a suggestion looks wrong, open an issue with what you typed before pressing Tab, what you expected, and your PowerShell and tool versions. Those examples help me decide what needs attention next.

PS7-Completion is available on GitHub under the MIT license. If a tool you use isn’t supported by the time you read this, open an issue and tell me which one. Include a few commands or options you’d like to complete so I know where to start.

I got tired of fixing my app windows every day, so I built Centre

Jack Scott — Fri, 12 Jun 2026 06:28:21 +0000

You know that tiny annoying thing you do every day but never really think about?

Opening your apps.

Moving them around.

Resizing them.

Putting the terminal here.

Putting the browser there.

Fixing the editor window.

Dragging that one app back from the weird corner of the screen.

Again.

And again.

It is not a “big problem”.

But it is one of those small repeated annoyances that slowly becomes part of your daily routine.

So I built Centre.

Centre is a small Windows tool that helps your apps remember where they belong.

Repository:

https://github.com/JackScott7/centre

The idea

I wanted something simple:

“This app should always go here.”

That’s it.

Not a full tiling window manager.

Not a huge productivity suite.

Not another app that needs 40 minutes of configuration before it becomes useful.

Just a small tool that lets you save a window position and bring it back when you need it.

Why?

Because I don’t want to manually rebuild my workspace every time.

My usual desktop setup is predictable:

terminal in one spot
browser in another
editor where I like it
tools arranged in a way that makes sense to me

But Windows does not always care.

Sometimes apps open in random places.

Sometimes they remember the wrong size.

Sometimes they appear slightly off.

Sometimes your workspace just feels messy before you even start working.

Centre tries to remove that friction.

The workflow

The workflow is basically:

Put a window where you want it.
Capture that position.
Restore it later with a shortcut.

That’s the whole point.

You arrange your workspace once, then stop thinking about it.

Preview

https://github.com/user-attachments/assets/d088a951-8c6b-4731-8228-80b063f1a6e5

This is not trying to be fancy

Centre is not trying to compete with PowerToys FancyZones.

It is not trying to replace a tiling window manager.

It is not trying to become a massive desktop automation platform.

It is intentionally small.

I built it because I wanted a lightweight tool that does one thing:

Make my windows go where I expect them to go.

That’s the kind of boring utility I actually end up using every day.

Who might like this?

The funny part

This project started from a small annoyance.

Not some huge architectural idea.

Not a startup pitch.

Just:

“Why am I still manually moving this window?”

And honestly, that is my favorite kind of project.

Small problem.

Small tool.

Immediate benefit.

Try it

Centre is open source and available on GitHub:

https://github.com/JackScott7/centre

It is also available on PyPI:

https://pypi.org/project/centre/

If you use Windows and constantly rearrange the same apps, give it a try.

And if you have ideas, feedback, edge cases, or weird Windows behavior to report, I’d genuinely like to hear it.

Because desktop workflow tools are always better when real people use them in real messy setups.

Get Notified When Long-Running Commands Finish in PowerShell 7

Jack Scott — Wed, 07 Jan 2026 01:10:27 +0000

Hey there.
I'm gonna give a simple trick to make your life easier when running time consuming commands in PowerShell 7.

So a while back I installed Arch Linux to see what the hype was about, I opened Konsole and noticed a notification pop up when the command I ran finished.

After a while I reinstalled Windows, and wanted to make that notification functionality work in PS7.

How this works?

This works by recording a timestamp when Enter is pressed and comparing it when PowerShell renders the next prompt. If execution time exceeds a threshold, a Windows toast notification is triggered. That's it.

If you’re hooked, Let’s make this happen.

Step 1

Install PS7 module by running:

> Install-Module BurntToast

Step 2

Run the following in PS7 to get the PS7 Profile path:

> $PROFILE

C:\Users\<username>\Documents\PowerShell\Microsoft.PowerShell_profile.ps1

Step 3

Open your profile in VS Code or whatever editor you use.

> code $PROFILE

Step 4

Import the Module you just installed

Import-Module BurntToast

This should always be at the top, otherwise the next steps won't work

Step 5

Copy and Paste this code at the top of your profile after importing the module

$OriginalPrompt = (Get-Command prompt).ScriptBlock   # capture original prompt

# Notification need a logo to use, so we'll be using PowerShell's icon
$applogo = "C:\Program Files\PowerShell\7\assets\Powershell_av_colors.png"

$ExecutionNotifyThreshold = 3 # seconds
$global:__commandStart = $null

# To format timestamp as human readable as possible
function Format-Elapsed([TimeSpan]$timestamp) {
    if ($timestamp.TotalSeconds -lt 60) {
        return ('{0:0.0}s' -f $timestamp.TotalSeconds)
    }

    $parts = New-Object System.Collections.Generic.List[string]

    if ($timestamp.Days -gt 0)    { $parts.Add("{0}d" -f $timestamp.Days) }
    if ($timestamp.Hours -gt 0)   { $parts.Add("{0}h" -f $timestamp.Hours) }
    if ($timestamp.Minutes -gt 0) { $parts.Add("{0}m" -f $timestamp.Minutes) }

    $remainingSeconds = [math]::Floor($timestamp.TotalSeconds % 60)
    $parts.Add("{0}s" -f $remainingSeconds)

    return ($parts -join ' ')
}

function global:prompt {
    if ($global:__commandStart) {
        $elapsed = (Get-Date) - $global:__commandStart
        if ($elapsed.TotalSeconds -ge $ExecutionNotifyThreshold) {
            $lastCmd = (Get-History -Count 1).CommandLine
            $text = @(
                'PS7 Finished:'
                "`$ $lastCmd"
                ("Took {0}" -f (Format-Elapsed $elapsed))
            )
            New-BurntToastNotification -Text $text -AppLogo $applogo
        }
        $global:__commandStart = $null
    }
    & $OriginalPrompt
}

$ExecutionNotifyThreshold is the time window you want to be notified when the command is taking longer than this threshold. Adjust as you wish

We have one last step and we are done, keep going 😁🚀

Step 6

Now add the below code at the end of your $PROFILE

This should always be at the end, so nothing else will override your custom functionality

Set-PSReadLineKeyHandler -Key Enter -ScriptBlock {
    $global:__commandStart = Get-Date
    [Microsoft.PowerShell.PSConsoleReadLine]::AcceptLine()
}

Now Save the file, restart your shell (you can also run ". $PROFILE" to restart PS7)
run a command that will take longer than your threshold, you should see a similar Notification pop up like this:

Notes & Caveats

I have been using oh-my-posh with this approach for a year now and had no problems so far
This overrides the global prompt function. If you use oh-my-posh, starship, or another prompt framework, load this after your prompt is configured.
This hooks the Enter key via PSReadLine. If you already have a custom Enter handler, you’ll need to merge the logic.
To remove the behavior:

  Remove-PSReadLineKeyHandler -Key Enter

That's it! you're Done. Congrats 🥳

This removes the need to babysit long-running commands and keeps you informed without breaking flow.

Tell me what you think about this approach. ❤️

Reset Windows 10/11 Password Without USB or Reinstall

Jack Scott — Wed, 23 Jul 2025 20:26:34 +0000

Hi there, Its jack, i got locked of my machine 10 minutes before posting this, i thought maybe this post might help some folks out :)

TL;DR (2 minutes)

Boot into Windows Recovery Environment (WinRE).
Swap utilman.exe with cmd.exe on *C:*.
On the login screen, hit Ease of Access → instant SYSTEM cmd.
Run: net user "YourUser" NewPass123!.
Log in, then restore utilman.exe to close the backdoor.

Done. No USB sticks, no reinstall.

Copy/Paste Cheat Sheet

:: WinRE Command Prompt (assumes Windows on C:)
bcdedit | find "osdevice"                :: optional sanity check
copy C:\Windows\System32\utilman.exe C:\Windows\System32\utilman.bak
copy C:\Windows\System32\cmd.exe     C:\Windows\System32\utilman.exe
exit                                      :: reboot

:: Login screen → Ease of Access shell
net user                                   :: list users
net user "YourUser" NewPass123!
exit

:: After logging in (Admin cmd)
copy C:\Windows\System32\utilman.bak C:\Windows\System32\utilman.exe

Why This Works (30 seconds)

utilman.exe (Ease of Access) runs before you sign in. Replace it with cmd.exe, click the icon on the login screen, and you get a SYSTEM shell. SYSTEM can change local passwords. Afterwards, put utilman.exe back. Boom.

⚠️ BitLocker alert: If the drive is locked with BitLocker, you’ll need the recovery key before you can touch C:\Windows\System32.

Step 0: Force Windows Into WinRE

Can’t log in? Crash it into recovery:

Power on.
When you see spinning dots, hold power to force shutdown.
Do it twice. On the third boot: Preparing Automatic Repair → Advanced options.

Then: Troubleshoot → Advanced options → Command Prompt.

You’ll land at something like:

X:\Sources>

Step 1 (Optional): Verify Windows Drive Letter

It’s usually C:. If you want to be sure:

bcdedit | find "osdevice"

Sample output:

osdevice partition=C:

If it says C:, keep following as-is. If not, swap the letter in the commands below.

Step 2: Backup utilman.exe & Drop In cmd.exe

Commands (assuming Windows is on C:):

copy C:\Windows\System32\utilman.exe C:\Windows\System32\utilman.bak
copy C:\Windows\System32\cmd.exe     C:\Windows\System32\utilman.exe

Overwrite prompt? Type Yes.

Type exit and reboot.

Step 3: Pop a SYSTEM Shell From the Login Screen

At the login screen, click the Ease of Access icon (bottom-right). Instead of accessibility tools, you get Command Prompt as SYSTEM.

List users so you don’t guess wrong:

net user

Reset the password (exact username, wrap in quotes if it has spaces, e.g. Jack):

net user Jack MyNewPassword

You should see: The command completed successfully.

Close the window, log in with the new password.

Step 4: Restore utilman.exe (Don’t Leave a Door Open)

This step is optional, since it doesn't mess up your system, but security wise, its recommended to do.

Inside Windows, open Command Prompt as Administrator:

copy C:\Windows\System32\utilman.bak C:\Windows\System32\utilman.exe

Y to overwrite.

That closes the backdoor — the Ease of Access button works normally again.

Troubleshooting & Gotchas

“Access is denied” / Error 5

You didn’t get a SYSTEM shell. Make sure you clicked Ease of Access after the swap.

Username typos

Run net user first. Match the exact name, or wrap it in quotes.

Messed up the wrong file / forgot to restore

Boot back to WinRE and reverse it:

copy C:\Windows\System32\utilman.bak C:\Windows\System32\utilman.exe

BitLocker prompt

No key, no access. Period.

Microsoft or Domain accounts

Microsoft account: Use the online reset: https://account.live.com/password/reset
Domain machine: Talk to your admin. This only resets local accounts.

Final Notes

This is a break-glass move, not routine hygiene. Use a password manager, link a recovery email/phone, or create a reset disk so you don’t need this again.
If this saved you time/money/your sanity, drop a thanks — and document your own “oh crap” fixes for Future You.

Hope i could help you :)

Happy un-locking 👊

🚀 Meet IntelliText: The Power Tool for Text Automation You Didn’t Know You Needed

Jack Scott — Wed, 06 Nov 2024 07:31:54 +0000

Hi There

Ever felt bogged down by repetitive typing tasks? 😫 Whether you’re a developer, writer, or anyone who types a lot, IntelliText is here to save you time. This Python-based tool listens to your keyboard input, auto-inserting text or performing actions based on custom macros. Say goodbye to redundancy and hello to productivity! 💪

✨ What is IntelliText?

IntelliText is your new best friend for automating frequent text and commands. It’s designed to manage word macros and action macros through customizable shortcuts. For instance:

Word Macros 📝: Type !email, and IntelliText can insert your entire email signature. Or !addr could fill in your address.
Action Macros ⚙️: Need to quickly paste clipboard content? Use #cb to instantly insert it, or create a macro like #deploy to launch your favorite script.

With its extension support, IntelliText is adaptable to any unique workflow, ensuring it grows with your needs. 🔧

🔑 Key Features You’ll Love

Custom Macros 🛠️: Build your shortcuts in macros.json for fast, flexible text handling.
Action Automation ⚡: From launching apps to pasting data, use # triggers to reduce redundant steps.
Extension Support 📦: Add your own functions or scripts and integrate them with IntelliText macros, expanding possibilities.
Macro Shuffle 🎲: Tired of typing the same things? Configure lists that shuffle outputs, like rotating programming languages or project tasks.

🚀 How to Get Started

Clone the Repo 📥: Get IntelliText from GitHub and install dependencies or install using pip.
Create Your Macros ✏️: Define your frequently used text or actions in the it_macros.json file.
Run IntelliText 🏃: With one click, IntelliText starts working with your macros, ready to simplify your workflow.

Examples: What Can IntelliText Do for You? 💡

Email Management 📧: Insert standardized replies with a shortcut. Type !thanks, and it can auto-fill a thank-you note.
Coding Shortcuts 💻: Use macros to insert commonly used code snippets or comments, saving time on boilerplate code.
Quick Data Access 📂: Set up #link to open frequently used resources like documentation or project files directly from IntelliText.

👥 Join the IntelliText Community

IntelliText is open-source and open for contributions! 💡 If you have ideas for more powerful macros or custom extensions, share them with the community! Get IntelliText, give it a star ⭐ on GitHub, and let’s make text management smoother together.