wise

Plugin wise from marketplace wise-claude in e1024kb/wise-claude. Commands read from the repo's manifest — yesterday.

Skills (41)

• wise-code-comments

  Code-comment rules for EVERY comment and docstring written on the user's behalf in ANY programming language. ALWAYS consult this skill before writing, rewriting, or reviewing a code comment, docstring, or inline annotation - whether adding comments to new code, editing code that carries comments, or

• wise-code-review

  Review local changes or a pull request with wise's 3-lens code review team (correctness, security, tests) on the harness, model and effort you pick per role: conducts the bundled `code-review` workflow, whose pre-flight asks harness, model and effort for each reviewer, the curator, the optional veri

• wise-commit-message

  Draft one Conventional-Commits subject line from your pending git changes — both staged (`git diff --cached`) and unstaged-but-modified tracked files (`git diff`) — ticket-scoped (e.g. `feat(PROJ-777): …`) when a key is detectable from the branch, diff, recent commits, or the live session, and unsco

• wise-commit-push

  Sweep every working-tree change into the index (`git add -A` — modifications, deletions, and new untracked files), draft a Conventional-Commits subject from the staged diff, run `git commit`, then `git push` to the tracked upstream. If the working tree is already clean but the local branch is ahead

• wise-commit

  Sweep every working-tree change into the index (`git add -A` — modifications, deletions, and new untracked files), draft a Conventional-Commits subject from the staged diff (ticket-scoped when a key is detectable from the branch / diff / log / session), and run `git commit`. Closes the loop that `/w

• wise-conductor

  Coordinate many parallel child sessions from one main thread: one `ticket-auto` child per tracker ticket, one plain session per topic, with two-way messaging, a persistent ledger, verified status reports and a review-comment round that sends each PR's unresolved threads to the child that owns the PR

• wise-estimation

  Story-point estimation reference — a Fibonacci 0.5 → 13 SP scale for sizing work across frontend, backend, mobile, and all teams, including how to size uncertain work and the "anything > 8 SP is a research ticket, not an implementation ticket" rule. Use whenever the user says "estimate", "story poin

• wise-exec-on-harness

  Execute one free-form prompt as a headless child on any supported harness (`claude`, `codex`, `cursor`, `gemini`, `grok`) at a model, effort and permission mode you choose. The first action is always a host inventory: which supported harnesses are installed and logged in. A `--on` value is validated

• wise-feedback

  Open a GitHub issue in e1024kb/wise-claude reporting feedback, a bug, or a suggestion about a wise skill or workflow — the submitter's environment (OS, Claude Code version, gh version, the cwd's public git remote as org/repo) is auto-captured and the Problem / Summary / Proposal sections are drafted

• wise-fork

  Reorient the agent after a session fork: inherited context becomes read-only background and pre-fork work stays with the original session. Every in-flight task, plan, and promise from before the fork is dropped, remembered file state is distrusted, and this session starts fresh parallel work - optio

• wise-grill

  Deep-research ANY underspecified subject — a tracker ticket (Jira, Linear, GitHub, …), a doc link (Confluence, Notion, RFC, Google Doc), or a free-form prompt / question — across every reachable source: the subject's own comments + screenshots, linked docs, Slack discussions, Google Drive, design fi

• wise-human-writing

  Human-first writing rules for EVERY outbound message composed on the user's behalf - ticket descriptions and comments in ANY issue tracker (Jira, Linear, GitHub Issues, GitLab, Asana, Monday, YouTrack, …), PR / MR descriptions, comments, and review replies on ANY code host (GitHub, GitLab, Bitbucket

• wise-implement-plan-auto

  Autonomously implement a written implementation plan (a `PLAN-*.md` produced by ticket-auto / ticket-plan / wise-revise) on the checked-out branch, on the wise engine: the bundled `impl-plan` workflow turns the plan's task waves into atomic commits, each task tidied and validated, nothing pushed. Pr

• wise-init

  Set up wise's Python 3.11+ runtime and managed engine dependencies, check the engine, report provider and connector readiness, and cache the results. GitHub, provider logins, SSH, MCP connectors, and markitdown are optional until a selected action needs them. Preserve earlier skip decisions on repea

• wise-insights-mine

  Mine your own Claude Code session history for recurring task patterns and, once a pattern recurs across enough distinct sessions, draft it into a reusable personal skill under ~/.claude/skills/ — after you approve each one. This is the wise self-improvement loop: a SessionEnd hook quietly records ea

• wise-insights-refine

  Review your learned skills for overlap and consolidate them — merge several redundant or composable skills into one aggregated skill and retire the originals (reversibly), after your approval. The "garden" pass to /wise-insights-mine's "harvest": mine creates skills from recurring sessions, refine k

• wise-insights-reset

  Reversibly clean up the self-improvement loop, and roll it back. Snapshots then removes the auto-created (wise-managed) skills and/or the insights index (ledger, candidates, decisions) into a timestamped restore point — and can restore any restore point. Never touches hand-written skills, and never

• wise-markitdown

  File-to-markdown text extraction via Microsoft's `markitdown` CLI — the ONE tool to reach for whenever text/content must be extracted from a binary or structured file: PDF, Word (.docx), PowerPoint (.pptx), Excel (.xlsx/.xls), images (EXIF metadata), audio (metadata + transcription), HTML, CSV/JSON/

• wise-pr-add-reviewers

  Request human reviewers on the PR for the current branch: ask whether to add reviewers, then propose candidates (CODEOWNERS, recent authors, org members) as picks plus free-text logins. Never requests a review bot (Copilot code review, CodeRabbit). Idempotent - already-requested reviewers are detect

• wise-pr-create-auto

  Autonomous variant of `/wise-pr-create` — detect the PR state for the current branch and create or refresh the PR with NO prompts. The body is drafted from the project's PR template; the base branch is chosen autonomously (the repo's default branch) instead of asked. Built for unattended ticket→PR r

• wise-pr-create

  Detect the PR state for the current branch and either create a new GitHub PR or refresh an existing one — body drafted from the project's `.github/pull_request_template.md` (or a bundled fallback) filled from the branch's diff + commits, ticket reference auto-detected from branch/diff/log/session, b

• wise-pr-watch-auto

  Autonomous variant of `/wise-pr-watch` — drive the checked-out branch's open PR to merge on the wise engine: the bundled `pr-watch` workflow polls CI and any review bot configured on the repo, runs wise's own local review (the 3-lens code review team) on each new head, fixes what they raise, pushes,

• wise-pr-watch

  Watch the current branch's PR and drive it to green: block on `gh pr checks --watch`, classify failing checks (lint / tests / other) and auto-fix them — committing via the shared Conventional-Commits routine — then walk four sequential review queues (humans → Copilot → CodeRabbit → Sonar), each gate

• wise-prd-architect

  Creates and iterates on Product Requirements Documents (PRDs) through structured discovery, parallel brainstorming agents, and collaborative refinement. Use this skill whenever the user mentions PRD, product requirements, product spec, feature spec, product brief, requirements document, or wants to

• wise-profile

  Set the session's token-budget profile — low, medium, or max — which every profile-sensitive wise skill and workflow reads at start to scale model tiers, optional research scope, reviewer-panel size, and retry caps. Budget only: it NEVER changes correctness rules (commit conventions, dirty-tree refu

• wise-report

  Produce a verified status report of the current session - what is done, what is not, the plan, next steps, open questions, leftovers, and postponed tasks - in compact ref-coded form (F facts, A actions, Q questions, R risks, L leftovers, P postponed), with every claim backed by checkable evidence (g

• wise-revise

  Point wise at a scope — a folder, a component, or the whole project — with a free-form improvement intent ("make the API faster", "pay down debt in src/auth", "raise test coverage", or just "improve this"), and it investigates the code read-only, decides what is worth doing, and writes self-containe

• wise-simplify-auto

  Autonomously simplify recently-modified code and commit it — runs the simplify pass over the working tree (the `code-simplifier` agent on Claude Code when installed, otherwise the same cleanup inline on the current model; behaviour preserved: clarity, consistency, dead-code/redundancy removal), then

• wise-skills-create

  Scaffold a new skill inside the wise plugin by delegating to Claude Code's skill-creator skill. The new skill lands in `plugins/wise/skills/<name>/`. The plugin hosts two skill shapes: standalone slash-command skills and reference/guidance skills. Any free-form tail the user types after the skill na

• wise-skills-edit

  Edit an existing wise plugin skill by delegating to Claude Code's skill-creator skill with the existing SKILL.md as the target and the wise plugin conventions as guardrails. Locates the skill under `plugins/wise/skills/`. Refuses the `wise` natural-language helper (editing it changes the plugin's di

• wise-ste

  Rewrite a draft, a file, or your last response in ASD-STE100 Simplified Technical English, with short sentences, active voice, one instruction per sentence and one term per thing, and return the result without posting it anywhere. Invoked as `/wise-ste` (bare alias) or `/wise:wise-ste` (canonical).

• wise-supervise

  Attach a supervisor / watchdog loop to a running team of background agents and keep them on task — automates the manual "ping all your subagents, are you still on track?" nudge. Reads the team's members, actively probes each for its status, nudges any that are idle-but-unfinished or off-goal, and es

• wise-tickets

  Ticket-writing rules for EVERY ticket composed on the user's behalf in ANY issue tracker (Jira, Linear, GitHub Issues, GitLab, Asana, …) or tracker-like system. ALWAYS consult this skill before creating, editing, updating, splitting, or breaking down a ticket or epic, whichever MCP server, CLI, or A

• wise-trd-architect

  Creates and iterates on Technical Requirements Documents (TRDs) — the engineering counterpart to a PRD. Translates product requirements into architecture decisions, API contracts, data models, and implementation roadmaps. Use this skill when the user mentions TRD, technical design, technical spec, a

• wise-workflow-create

  Create a workflow from a free-form prompt. Automatically infer its name, settings, steps and dependencies, then ask for harness, model and effort for each model-executing step in sequence. Validate and save YAML + README without additional authoring questions. Use when the user says "create a workfl

• wise-workflow-list

  List every workflow available to the wise plugin — both the bundled defaults that ship with the plugin and the user-authored ones under the engine-selected user definition directory. Read-only. Invoked as `/wise-workflow-list` (bare alias) or `/wise:wise-workflow-list` (canonical). Use when the user

• wise-workflow-remove

  Delete a user-authored workflow definition from `the engine-selected user definition directory` — handles both layouts (`<name>/workflow.yaml` folder form AND legacy `<name>.yaml` flat form). Refuses to touch bundled workflows — they ship with the plugin and are replaced by a reinstall, not a remove

• wise-workflow-resume

  Resume a paused or failed workflow run on the wise engine, or answer the gate of a gated one, then follow its events in this conversation. Invoked as `/wise-workflow-resume` (bare alias) or `/wise:wise-workflow-resume` (canonical). Use when the user says "resume the workflow", "continue the paused r

• wise-workflow-run

  Start a workflow run on the wise engine: pre-flight questions, run context from the conversation, one line per engine event, gates. Invoked as `/wise-workflow-run` (bare alias) or `/wise:wise-workflow-run` (canonical). Use when the user says "run the workflow", "kick off <workflow-name>", or types `

• wise-workflow-status

  Show workflow runs on the wise engine. With no argument, list every run with its status, workflow, start time, cwd and live children. With a run ULID, show that run; when it is gated, show the gate and offer to answer it. Invoked as `/wise-workflow-status` (bare alias) or `/wise:wise-workflow-status

• wise

  wise copilot — natural-language entry point for the whole wise plugin. With no argument, prints the catalog of available `/wise-*` commands plus the reference skills; with free-text (e.g. `/wise open a PR`, `/wise draft a commit message`), classifies the request against the catalog and offers to run

Subagents (13)

• architect

  Use for system and component design — choosing patterns, defining boundaries and data flow, weighing trade-offs (scalability, consistency, cost, complexity), and recording decisions ADR-style. Pick this for any workflow step that must decide *how* something is built before it is built, or that produ

• ceo

  Use for the highest-altitude business calls — prioritizing across competing initiatives, framing a trade-off in terms of value, risk, cost, and timing, or making a go / no-go decision. A chief executive who sets direction and names what's out of scope. Pick this for any workflow step that needs a st

• code-reviewer

  Use for reviewing a diff or branch — correctness bugs, security issues, and clear quality problems, severity-tagged, one finding per line, no praise, no scope creep. A staff-level reviewer who finds and explains but does not rewrite. Pick this for any workflow step that gates a change on review befo

• cto

  Use for technical strategy calls — build-vs-buy, platform and tech-stack direction, technical-risk assessment, and arbitrating cross-team architecture disputes. A chief technology officer who sets direction and delegates detailed design. Pick this for any workflow step that needs a binding technical

• devops-engineer

  Use for CI/CD, infrastructure-as-code, containerization, and deployment strategy — authoring or fixing pipelines, Dockerfiles, Terraform/Helm/k8s manifests, and choosing a safe rollout (blue-green, canary) with a rollback path. A senior DevOps engineer who verifies with a dry run or plan output befo

• engineering-manager

  Use to turn an approved plan or goal into a sequenced delivery plan — decomposing work into tasks with acceptance criteria, estimating effort, mapping dependencies into parallelizable waves, and flagging risks and blockers. Pick this for any workflow step that plans *who-does-what-and-when* before c

• product-manager

  Use to turn a problem into crisp requirements — user stories, testable acceptance criteria, MVP-vs-later scope, and prioritization grounded in user and market reality. A senior PM who validates the problem before speccing the solution. Pick this for any workflow step that produces requirements or sc

• qa-engineer

  Use for test strategy and quality — enumerating edge cases, designing a test plan, writing or extending automated tests and running them, and filing precise, reproducible defect reports. Pick this for any workflow step that decides *what to test and how* or that hardens a change with coverage, rathe

• security-engineer

  Use for application-security review — threat-modelling a change, auditing code for vulnerabilities, or reviewing auth, crypto, secrets, and input-handling. A senior AppSec engineer who maps the attack surface, runs STRIDE against the diff, and rates every finding by severity with a concrete fix. Pic

• software-engineer

  Use for hands-on implementation — building a feature, fixing a bug, refactoring, or writing tests against an existing codebase. A senior, polyglot engineer who reuses what's there before writing new code and leaves the tree working. Pick this for any workflow step that turns a decided plan or a well

• sre

  Use for reliability, observability, and operability — defining SLIs/SLOs and error budgets, designing monitoring/alerting on the golden signals, capacity planning, and writing incident-response runbooks. A senior SRE who reasons about failure modes and turns them into measurable goals and actionable

• technical-writer

  Use for developer-facing documentation — READMEs, API references, how-to guides, changelogs, and inline doc comments. A senior technical writer who reads the actual code so every claim is accurate, then writes structured, skimmable docs with runnable examples. Pick this for any workflow step that pr

• ux-designer

  Use for experience design — mapping a user flow, designing interaction and information architecture, auditing usability and accessibility (WCAG), or critiquing a proposed or existing UI. A senior UX/UI designer who delivers an experience spec, not production CSS. Pick this for any workflow step that

Hooks (3)

• SessionEnd

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/session-end-ingest.sh"

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/session-start-style.sh" SessionStart

• SubagentStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/session-start-style.sh" SubagentStart

Similar plugins