Back to authors
scizorman

scizorman

12 Skills published on GitHub.

git-operator

Rules and procedures for Git operations (add, branch, commit, push). Use when performing git add, git commit, git push, or creating branches.

UncategorizedView skill →

github-issue-commenter

Posts work report comments to GitHub Issues or PRs using gh CLI. Use when reporting completed work, posting progress updates, summarizing changes made in a session, or adding structured comments to issues or PRs. Also use when the user says "issue にコメントして", "作業報告して", or "進捗を報告して".

UncategorizedView skill →

github-issue-creator

Creates GitHub issues using gh CLI. Use when creating new issues.

UncategorizedView skill →

github-pr-creator

GitHub CLI で Pull Request を作成する。実装完了後や変更 push 後に PR を提出したい時に使用する。

UncategorizedView skill →

github-project-operator

Manages GitHub Projects v2 write operations using gh CLI. Use when adding issues or PRs to a project, creating tasks (issues) in a project, updating field values (Status, Priority, Size, Sprint, etc.), creating draft issues, creating fields, or archiving items. Also use at the start of a session when selecting a project to work with.

UncategorizedView skill →

github-project-reporter

Reads and analyzes GitHub Projects v2 data using gh CLI. Use when listing items by status, extracting high-priority tasks, generating sprint progress summaries, detecting blockers or health issues (unassigned items, overdue items, WIP excess), or producing progress reports.

UncategorizedView skill →

github-sub-issue-creator

Creates GitHub sub-issues and links them to parent issues using gh CLI and REST API. Use when creating child issues, breaking down large issues into smaller tasks, or establishing parent-child relationships between issues.

UncategorizedView skill →

project-charter-creator

Use this skill whenever the user wants to create, draft, or improve a Project Charter. Triggers include: any mention of 'project charter', 'charter', 'プロジェクト憲章', 'プロジェクトチャーター', 'プロジェクト企画書', or requests to formally authorize a project, define project scope and objectives, align stakeholders, or establish project governance. Also use when the user says 'プロジェクトの立ち上げ', 'プロジェクトの認可', 'キックオフ文書', or mentions needing to get sponsor approval for a project. This skill covers project charters for any methodology (Waterfall, Agile, Lean Six Sigma) and any domain (IT, construction, marketing, organizational change, product development, etc.). Use this skill even if the user just says 'help me start a project' or 'I need to get alignment on my project'.

UncategorizedView skill →

project-plan-creator

Creates project management plans in Markdown. Use when creating project plans, defining how to manage scope/schedule/risk/communication, or detailing project execution strategy. Primarily for internal projects that build systems, processes, or organizational capabilities.

UncategorizedView skill →

rfi-creator

Use this skill whenever the user wants to create, draft, or improve a Request for Information (RFI) document. Triggers include: any mention of 'RFI', 'Request for Information', 'information request to vendors', '情報提供依頼書', 'ベンダー情報収集', or requests to explore what vendors or solutions exist in a market before issuing an RFP. Also use when the user wants to compare vendor capabilities at an exploratory stage, gather market intelligence, or create a shortlist of potential suppliers. This skill covers RFIs for any domain: IT systems, SaaS, consulting, construction procurement, marketing, and more. Do NOT use this skill for RFPs (detailed proposal requests with requirements and pricing) or RFQs (pricing-only requests) — use the rfp skill for RFPs instead. If the user is unsure whether they need an RFI or RFP, help them decide based on how well-defined their requirements are.

UncategorizedView skill →

rfp-creator

Use this skill whenever the user wants to create, draft, or improve a Request for Proposal (RFP) document. Triggers include: any mention of 'RFP', 'Request for Proposal', 'proposal request', 'vendor selection document', 'procurement document', or requests to create documents for soliciting bids from vendors/suppliers. Also use when the user mentions '提案依頼書' (Japanese RFP), 'ベンダー選定', or similar procurement-related document creation in any language. This skill covers RFPs for any domain: IT systems, construction, marketing, consulting, software development, MDM, ERP, and more. Use this skill even if the user just says 'help me write an RFP' or 'I need to compare vendors for a project'. Do NOT use for RFP *responses* (vendor-side proposal writing) or general report/memo creation.

UncategorizedView skill →

self-critique

Analyze your own previous response with rigorous self-critique

UncategorizedView skill →