hiroro-work
- 26 skills
- 0 followers
- 1 week ago last updated
- ▌ Rules Review · hiroro-work bundleCheck code changes for .claude/rules/ compliance. Use this skill when you need to verify that code changes follow project coding rules, whether as part of dev-workflow or standalone. Triggers on: rule compliance check, rules review, verify conventions, check coding standards. Best suited for hard rules (naming, imports, placement, explicit prohibitions); intent-style rules are checked on a best-effort basis.
- ▌ Extract Rules · hiroro-work bundleExtract project-specific coding rules and domain knowledge from existing codebase, generating markdown documentation for AI agents. Use when onboarding a new project, after code review discussions about coding style, or when coding conventions need documenting. Also consider running after sessions where coding preferences were discussed or corrected (--from-conversation), or after PRs with significant review feedback (--from-pr).
- ▌ Security Scanner · hiroro-work bundleScan installed plugins and skills for security risks including malicious code AND malicious natural language instructions. Use /security-scanner to audit before installation.
- ▌ Inbox Add · hiroro-workRead .claude/inbox-add.local.md and append one task line to the Obsidian Vault's inbox.md. Use when the user requests "add to inbox", "inboxに追加", "これをinboxに入れて", or any equivalent task-capture intent.
- ▌ Run Tests · hiroro-workVerify plugins marketplace structure, version consistency, and JSON/frontmatter validity via subagent
- ▌ Verify Diff · hiroro-work bundleEmpirically verify that a code diff achieves its stated objective by dispatching a bias-free executor that actually runs auto-derived evaluation scenarios against the post-diff file. The executor returns a JSON verdict with `suggested_edits`, and this skill applies them — a single pass by default, or iteratively up to `Max iterations` when the caller raises it. Non-interactive — no user prompts. Use after applying an Edit when you need a dynamic cross-check that complements static reviewers like skill-review.
- ▌ Skill Review · hiroro-work bundleReview uncommitted skill changes against an internal checklist of skill-creator best practices and apply improvements. Use this whenever the user asks to "review skills", "check best practices", "improve SKILL.md", or wants a quality check on skill files before committing. Use this when there are uncommitted diffs in SKILL.md, README.md, or references/ files under skills/ or .claude/skills/. This is for reviewing existing skill changes, not creating new skills from scratch. Runs standalone — no external skill dependencies.
- ▌ Prompt Tuning · hiroro-workMethodology for iteratively improving agent-facing instructions (skills / slash commands / CLAUDE.md / code-gen prompts) by having a bias-free executor run them and evaluating two-sidedly (executor self-report + instruction-side metrics) until improvements plateau. Use after creating or revising a prompt or skill.
- ▌ Work Complete · hiroro-workWork completion handler. Archives the plan file. Example: /work-complete
- ▌ Run Node Tests · hiroro-workRun the repository's Node test suite under tests/ via `node --test` and report a structured verdict. Project-local routine — not for marketplace distribution.
- ▌ Verify Bundle Sync · hiroro-workVerify the dev-workflow-bundle canonical and bundle copy directories are in sync. Workaround for upstream symlink bug; delete this skill and its callers when symlinks are restored.
- ▌ Extract Skill Section · hiroro-workExtract a named SKILL.md section's body verbatim into a references/<name>.md file, replace the body with a skeleton (section label + delegation pointer, runtime definitions left in place), sync the bundle copy, and verify byte-identity plus cross-reference integrity via the repository's reference test and verify-bundle-sync. One-command automation of the manual section-extraction procedure used to shrink oversized SKILL.md files. Non-interactive — no user prompts. Project-local routine — not for marketplace distribution.
- ▌ Review With Untracked · hiroro-workTemporarily visualize untracked new files into the git diff so a chain of diff-deriving review callees can see them, then restore the files to untracked. Runs `git add -N` on untracked new files (intent-to-add), dispatches the requested review callees (rules-review / skill-review / publicity-review / verify-diff / tidy) in order, then `git reset -- <paths>` to restore the untracked state. Holds a closed list of each callee's visualization and restore-safety assumptions. Non-interactive — no user prompts. Project-local routine — not for marketplace distribution.
- ▌ Tr · hiroro-workTranslate text between Japanese and English. Auto-detects source language. Use --hq for high-quality (sonnet), --fast for standard (haiku).
- ▌ Tidy · hiroro-work bundleReview changed code for reuse, quality, and efficiency, then apply cleanup edits. Dispatches a fresh host-provided reviewer per iteration when available; the main thread applies mechanical edits and re-dispatches until no further edits remain. Non-interactive — no user prompts. Use after implementation as a code-cleanup pass complementary to correctness review.
- ▌ Mobpro · hiroro-work bundleLearning-oriented development workflow (mob-programming style) for a junior navigator — the AI drives and narrates, the junior reviews each implementation unit's diff and approves commits. A thin entry point that runs dev-workflow in mob mode. Use instead of plain dev-workflow when the goal is to develop a feature while a junior learns from it.
- ▌ Ask Agy · hiroro-work bundleAsks Antigravity CLI for coding assistance. Use for getting a second opinion, code generation, debugging, or delegating coding tasks.
- ▌ Ask Peer · hiroro-work bundleConsult with a peer engineer for plan review, code review, implementation discussions, or problem-solving brainstorming. Use when you need a second opinion, want to validate your approach, or check for overlooked issues.
- ▌ Ask Codex · hiroro-work bundleAsks Codex CLI for coding assistance. Use for getting a second opinion, code generation, debugging, or delegating coding tasks.
- ▌ Artifactor · hiroro-work bundleA background drawing hand for a one-page, picture-first HTML artifact that grows over a session — one agent dispatched once and resumed with a message each turn, the page republished to the same URL whenever a section changes, the chat never waiting for the drawing. Use it when a page should keep growing as a conversation goes on, invoked as `/artifactor [<subject>]` by the user or loaded with `Skill(artifactor) --caller` by a skill that supplies what the page holds; not for a one-time artifact, which the `Artifact` tool makes directly.
- ▌ Ask Claude · hiroro-work bundleAsks Claude CLI for coding assistance. Use for getting a second opinion, code generation, debugging, or delegating coding tasks.
- ▌ Ask Gemini · hiroro-work bundleAsks Gemini CLI for coding assistance. Use for getting a second opinion, code generation, debugging, or delegating coding tasks.
- ▌ Apply Rules · hiroro-work bundleApply organization-wide rules (from merge-rules output) to the current project. Detects tech stack, merges Principles, cleans up promoted patterns from .local.md, and fixes non-conforming files.
- ▌ Ask Copilot · hiroro-work bundleAsks Copilot CLI for coding assistance. Use for getting a second opinion, code generation, debugging, or delegating coding tasks.
- ▌ Merge Rules · hiroro-work bundleMerge extract-rules output from multiple projects into a unified portable rule set. Promotes .local.md patterns shared across projects to Principles format.
- ▌ Dev Workflow · hiroro-work bundleGuided development workflow — task decomposition, planning, peer plan review, approval, implementation, tidy, prose polish, check/test, rules compliance review, code review, completion hooks, interactive commits, rule updates — with a fixed difficulty-skip table, browser plan review, plan artifacts, an optional mob mode for a junior navigator, and a growth-controlled self-retrospective; no executors. Runs the same way every time so a junior engineer can follow along. Use when the user wants a feature built, a bug fixed, or code refactored.