Use when the user asks to prepare, cut, validate, tag, or publish a ClawBox desktop release. Covers the UTC date-based version flow (npm run release:version), release validation commands, release commit/tag creation, and pushing the matching v tag for the current package version that triggers GitHub Releases. Do not…
MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with task(category='quick', loadskills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
Manage Git commits using conventional commit format with atomic staging. Always generate plain git commands before running them and offer to let the user run them manually.
Organize starred GitHub repos into stable, clear lists: detect new stars, download READMEs into a local corpus, classify each repo against the taxonomy, and sync the approved mapping back to GitHub via gh. Use this when a user wants their starred repos sorted into lists, a recent batch of new stars filed…
Create a pull request OR update the description of an existing PR for the current branch. Handles repo PR templates, JIRA ticket extraction (including title prefix), a prose summary followed by implementation bullets with rationale, testing evidence, and screenshot prompts for UI/frontend changes. On FanDuel repos…
Export Dev Graph UI assets and dashboard data. Use when the user asks for structure SVG exports, timeline SVG/MP4 exports, per-commit SVGs, sprint-linked visuals, or dashboard/analytics JSON from the Dev Graph API.
Audit and establish or upgrade the canonical repository governance baseline. Use only when explicitly asked to bootstrap, standardize, or upgrade a repository; do not use for feature development or source-code restructuring.
Write a Japanese technical article for Zenn or Qiita in aiya000's own writing style, learned from his past articles, with the target platform decided from the current directory. Use when the user asks to write, draft, or rewrite a tech article, blog post, or note, or invokes /write-tech-note.
Review changes against coding and documentation standards (repo standards plus a list of style skills), then optionally fix the findings. Use when the user wants a style, standards or conventions review of a branch, a commit range or uncommitted work.
Operate Sophia CLI as an intent-first abstraction over Git for local repositories. Use when the user wants to initialize Sophia, open/manage Change Requests (CRs), define CR and task contracts, checkpoint task progress with explicit scope, inspect impact/validation/review/status context, repair metadata, and merge…
Open a browser-based diff viewer showing all current changes in a VS Code-style file tree with syntax-highlighted diffs. Live-reloads as files change. Use when the user wants to "see the diff", "show changes", "what did I change", or "open diff viewer".
GitHub Knowledge Base - Unified tool for managing local repos, discovering trending projects, and tracking tech hot topics. Use when: (1) searching local GitHub repos, (2) updating repo index, (3) discovering new repos via social media (Xiaohongshu, Twitter/X) and web search, (4) researching topics on Xiaohongshu, (5)…
Before accepting an agent's 'done / shipped / fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's dos verify and dos commit-audit — never the agent's own narration.
Analyze any Git repository in depth — understand architecture, debug across repo boundaries, review APIs, plan migrations, and evaluate libraries. Surfaces real function signatures, parameter types, return values, and source citations with exact file paths and line numbers. Eliminates hallucinated APIs by grounding…
Kicks off a new feature by finding the next incomplete phase in specs/roadmap.md, creating a git branch, interviewing the user about scope/decisions/context, and writing a dated spec directory under specs/ containing plan.md, requirements.md, and validation.md. Trigger when the user says "feature spec", "next phase"…
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.
Git diff for AI agent repository instructions. Shows the blast radius of AGENTS.md and CLAUDE.md changes. Use when Git cannot show which agent inherited the edit, a Codex vs Claude Code split, or why one path inherited a stack.
Git safety workflow for AI agents. Use when the request says checkpoint, rollback, commit hygiene, worktree isolation, ops-state, runtime-state checkpoint/restore, or release hygiene for this skill. Do NOT use for general git tutoring, everyday branching advice, or non-agent backup/version-control workflows.
Cut a new release by tagging a version and publishing via GitHub, which triggers the PyPI Trusted Publishing and docs-deploy workflows. Use when asked to "make a release", "cut a version", or "publish".
★not rated 19 3d agoASkillSpector: pass47 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: