skills

Maintain CHANGELOG.unreleased.md in psamvault-cli. When the user opens a PR with code changes, read the PR diff, write entries to the unreleased file, and open a separate PR for the changelog update so it merges cleanly alongside the code changes.

Guide new feature development from idea to build-ready plan: structured summary → multiple-choice questions → PLAN.md collaboration → handoff to plan and subagent-driven-development skills.

Publishes Python projects to TestPyPI and PyPI, then creates a GitHub version release. Use this skill when the user wants to publish, release, or ship a Python package, or asks to bump a version and push to PyPI. Requires a pyproject.toml in the project. Workflow: build -> TestPyPI -> user tests locally -> PyPI + GitHub release. Before the version bump, loads the granular-commits-pr skill to commit codebase changes individually. Also covers the post-release backup of the py-publish skill itself to the skills backup repo at C:\Users\USER\.copilot\skills (github.com/psam-717/skills).

Scans the current git repo for all untracked and modified files, examines their contents/diffs, generates meaningful commit messages, presents them to the user for verification, then stages and commits each file individually. After committing, optionally creates a new branch and opens a PR for major updates (seeks user approval first). Supports both interactive mode (user-confirmation required) and cron/ automated mode (no interaction, commits autonomously). Trigger phrases: "stage and commit", "commit my changes", "commit all files", "git commit", "commit my modified files", "create a commit message", "auto-commit cron job". Works on Windows (git-bash/PowerShell) and POSIX.

Commit each changed file individually with conventional commit messages, create a new feature branch, push, and open a PR. Used when the user wants fine-grained, file-level commits rather than squashing everything into one.

Performs a thorough, beginner-friendly breakdown of the entire current project. Reads every file in the codebase and produces an extensive explanation of what the project is, how it is structured, how data flows through it, and what every major piece of code does. Use this skill when asked to explain a project, walk through a codebase, give an overview of how something works, or onboard onto an unfamiliar repo.

Performs a thorough codebase review and debugging session. Scans all source files for bugs, security issues, logic errors, and code quality problems. Presents a full bug report to the user and waits for approval before making any changes. After approval, fixes only the approved bugs, then delivers a summary of every change made and a description of the application's current workflow. Use this skill when asked to review code, debug the codebase, find bugs, or audit code quality.

Designs, extends, and reviews database schemas for Python backend projects. Use this skill whenever the user wants to add a new table, add columns to an existing table, design relationships, create indexes, write a migration, or asks "how should I model this in the DB", "what columns do I need", "add a field to X", "create a table for Y", or "write a migration for Z". Also trigger when reviewing model files for correctness, consistency, or best practices. Works across different projects and tech stacks — always reads the project's existing models first to match its conventions before writing anything new.

Keeps project documentation up to date. Ensures every project has a README in its root directory with accurate, current information. For projects that already have a README, scans the codebase for changes and updates the README to reflect the current state. Also audits existing inline code comments and updates any that are stale or misaligned with the code they reference — but never adds new comments unless explicitly asked to. Use this skill when asked to update docs, refresh a README, sync documentation, or fix stale comments.

Performs a focused security audit of the codebase or specific tagged files. Scans for vulnerabilities early in every feature — covering injection, authentication, authorization, secrets exposure, dependency risks, data validation, and more. Presents a prioritised vulnerability report to the user and, upon approval, applies surgical fixes. Use this skill when asked to audit security, find vulnerabilities, harden code, or review tagged files for security issues.

Enforces a test-driven development workflow: writes failing tests first, waits for user confirmation, then writes the minimal implementation to pass them, then refactors. Use this skill when the user types /tdd, says "write tests first", "TDD this", "test-driven", or "write tests for X before implementing it". Also trigger when the user asks to implement a non-trivial function, service, or feature and hasn't mentioned tests yet — proactively suggest the TDD cycle. Skips the ceremony for clearly trivial tasks (one-liners, pure config, simple data classes with no logic). Adapts to any language and test framework — always reads the project first.