Standardize branding to PowerCat and update documentation

[TheOnliestMattastic]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Standardize PowerCat branding and document new features

📝 Documentation ✨ Enhancement

Walkthroughs

Description

• Standardize branding from "POWERcat" to "PowerCat" across all documentation and code
• Add unreleased features to changelog: -WhatIf dry-run mode, -IncludeTree directory structure,
  global .catignore support, and -Verbose output
• Remove "Preview mode" from future roadmap (now implemented as -WhatIf)
• Update README with new feature highlights and improved feature descriptions

Diagram

flowchart LR
  A["Branding Updates"] --> B["POWERcat → PowerCat"]
  C["Feature Documentation"] --> D["Add Unreleased Section"]
  D --> E["WhatIf, IncludeTree, Catignore, Verbose"]
  F["Roadmap Cleanup"] --> G["Remove Preview Mode"]
  B --> H["Updated Docs"]
  E --> H
  G --> H

Loading

File Changes

1. src/PowerCat/PowerCat.psm1 📝 Documentation +1/-1

Update branding in module documentation

• Updated branding reference from "POWERcat" to "PowerCat" in module documentation notes
• Corrected CatIgnore behavior documentation header

src/PowerCat/PowerCat.psm1

---

2. CHANGELOG.md 📝 Documentation +13/-6

Add unreleased features and standardize branding

• Added new "Unreleased" section documenting four new features: -WhatIf dry-run mode,
 -IncludeTree directory structure, global .catignore support, and -Verbose output
• Standardized all "POWERcat" references to "PowerCat" throughout changelog
• Updated script wrapper path from scripts/POWERcat.ps1 to scripts/PowerCat.ps1
• Removed "Preview mode" from future roadmap (now implemented as -WhatIf)
• Updated command aliases and help references to use new branding

CHANGELOG.md

---

3. README.md 📝 Documentation +45/-43

Rebrand to PowerCat and enhance feature documentation

• Standardized all "POWERcat" references to "PowerCat" in title, badges, links, and content
• Added new feature descriptions for -WhatIf/Verbose and -IncludeTree capabilities
• Updated all code examples and command references to use new branding
• Updated demo descriptions and GIF alt-text to reflect new branding
• Updated comparison table header and feature descriptions

README.md

---

View more (2)

4. RELEASING.md 📝 Documentation +5/-5

Update release checklist with new branding

• Updated release checklist title to use "PowerCat" branding
• Updated file references from POWERcat.psd1 to PowerCat.psd1
• Updated git commands and PowerShell Gallery lookup commands to use new branding

RELEASING.md

---

5. ReleaseNotes.md 📝 Documentation +9/-9

Standardize PowerCat branding in release notes

• Standardized all "POWERcat" references to "PowerCat" throughout release notes
• Updated command aliases and help references to use new branding
• Updated historical version notes to reflect consistent branding

ReleaseNotes.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Script parity claim incorrect 🐞 Bug ≡ Correctness

Description

CHANGELOG states scripts/PowerCat.ps1 mirrors the module and accepts the same flags, but the
script’s parameter list does not include -WhatIf or -IncludeTree, and it lacks
[CmdletBinding()] so -Verbose is not supported, causing parameter-binding failures for users
following the docs.

Code

CHANGELOG.md[31]

Evidence

The changelog explicitly claims script/module flag parity, but the script’s param block omits
-WhatIf/-IncludeTree while the module defines and implements them and emits verbose progress via
Write-Verbose.

CHANGELOG.md[28-32]
scripts/PowerCat.ps1[117-209]
src/PowerCat/PowerCat.psm1[118-213]
src/PowerCat/PowerCat.psm1[406-444]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The changelog claims the standalone script wrapper accepts the same flags as the module, but it does not currently define key flags that are documented as supported (`-WhatIf`, `-IncludeTree`) and it is not an advanced script (`[CmdletBinding()]`), so `-Verbose` cannot be used.

### Issue Context
- Module `Invoke-PowerCat` defines `-WhatIf` and `-IncludeTree` and uses `Write-Verbose`.
- `scripts/PowerCat.ps1` defines a `-Help` parameter set and ends its param list at `-Stats`.

### Fix Focus Areas
- CHANGELOG.md[28-32]
- scripts/PowerCat.ps1[117-209]
- src/PowerCat/PowerCat.psm1[118-213]
- src/PowerCat/PowerCat.psm1[406-444]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. ProjectUri still POWERcat ✓ Resolved 🐞 Bug ⚙ Maintainability

Description

README now points to the PowerCat repository, but the module manifest ProjectUri still points to
.../POWERcat, so PowerShell Gallery metadata will direct users to the wrong repo.

Code

README.md[R5-6]

Evidence

The README update establishes the intended canonical repo name/URL (PowerCat), but the manifest’s
ProjectUri still points to the old POWERcat URL, which is what gets published to PSGallery
metadata.

README.md[5-6]
src/PowerCat/PowerCat.psd1[46-54]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The module manifest metadata still advertises the old POWERcat GitHub repository URL via `ProjectUri`, while the README was updated to the new PowerCat repo. This will cause PowerShell Gallery consumers to be routed to the wrong project link.

### Issue Context
README badges/links now reference `https://github.com/TheOnliestMattastic/PowerCat`, but `src/PowerCat/PowerCat.psd1` still uses `https://github.com/TheOnliestMattastic/POWERcat`.

### Fix Focus Areas
- src/PowerCat/PowerCat.psd1[46-60]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

3. Release checklist path inconsistent ✓ Resolved 🐞 Bug ⚙ Maintainability

Description

RELEASING.md refers to PowerCat.psd1 without a path, but CI/tests reference the manifest under
src/PowerCat/PowerCat.psd1, making the release checklist inconsistent with the repo’s actual
manifest location used elsewhere.

Code

RELEASING.md[48]

Evidence

The release checklist uses a bare filename, while both the GitHub Actions workflow and the Pester
tests refer to the manifest under src/PowerCat/PowerCat.psd1, demonstrating inconsistent
instructions vs. the repo’s established usage.

RELEASING.md[34-51]
.github/workflows/pester.yml[41-48]
tests/PowerCat.Tests.ps1[2-4]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The release checklist references `PowerCat.psd1` without the directory path. Elsewhere in the repo (CI and tests), the manifest is referenced via `src/PowerCat/PowerCat.psd1`, so the checklist should match that to avoid confusion during releases.

### Issue Context
This PR updates the checklist’s filename casing/branding, which is a good time to also standardize the path.

### Fix Focus Areas
- RELEASING.md[34-51]
- .github/workflows/pester.yml[41-48]
- tests/PowerCat.Tests.ps1[2-4]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[gemini-code-assist]

Code Review

This pull request primarily focuses on rebranding the project from 'POWERcat' to 'PowerCat' across all documentation and source files. Additionally, it introduces several new features, including a dry-run mode (-WhatIf), directory tree visualization (-IncludeTree), global .catignore support, and verbose output for progress tracking. The review feedback identified and provided corrections for several typos in the image alt text within the README.md file.