Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

shas9

@shas9 source repo

4 published skills

  1. ▌
    Issue Queue · shas9
    Work through a batch of pasted issues, code-review comments, bug reports, or audit findings one at a time — triaging by severity, validating each against the current code, confirming with the user before implementing, verifying, and committing in small chunks. Use this whenever the user pastes multiple issues, review comments, a QA list, or a findings dump and wants them addressed, fixed, or worked through — even if they don't say "one at a time" or name a process. Also use when the user says things like "address these review comments", "here are the bugs, fix them", "let's go through these issues", or asks to plan and fix a group of problems together.
    0 installs
  2. ▌
    Prompt Executor · shas9
    ONLY invoke this skill when the user's message literally begins with the trigger "PE:" (e.g. "PE: go") or is exactly the command "/claude-prompt-execute". Do NOT invoke based on general requests to "run this" or "do it" that don't use the literal trigger. If the literal trigger is not present at the start of the user's message, this skill must not activate.
    0 installs
  3. ▌
    Prompt Architect · shas9 bundle
    ONLY invoke this skill when the user's message literally begins with the trigger "PA:" (e.g. "PA: refactor the auth module") or is exactly the command "/claude-prompt-architect" (optionally followed by more text on the same line). Do NOT invoke based on similar-sounding requests such as "write me a prompt for X", "help me prompt Claude to do Y", or "can you design a prompt" — those are NOT triggers on their own. If the literal trigger text is not present at the start of the user's message, this skill must not activate, even if the task looks like prompt design.
    0 installs
  4. ▌
    Chunked Commit Review · shas9
    Split a messy working tree into small, reviewed, independently-valid commits — one logical change at a time, with a human approval gate that is configured once at the start of the session. Use this whenever the user has uncommitted changes they want broken into multiple commits, or says things like "let's go through the diff", "commit these chunk by chunk", "break this into commits", "review my changes before I commit", "clean up history before the PR", or wants to work through a batch of code issues together. Trigger even when the word "chunk" never appears — any request to split, review, or gate commits belongs here. Do NOT use for a single quick commit of everything.
    0 installs