jitsusama
39 verified skills189 total stars
code-investigation-guide
How to research and present findings about a codebase. Reading code, tracing flows, summarizing architecture. Use when understanding, exploring or explaining existing code before proposing changes.
development5
git-commit-convention
Operational commit rules: when to commit, what goes in each commit, commit frequency and history management. Use when committing code, deciding commit boundaries or managing git history. Pairs with commit-format for message structure.
development5
github-pr-merge-convention
PR merge strategy, branch cleanup and post-merge hygiene for any pull request. Use when merging a PR, cleaning up after a merge or deciding how to land changes. See github-pr-stack-convention when PRs depend on other PRs.
testing5
github-pr-reply-guide
Responding to GitHub PR review feedback. Workflow for analyzing review threads, implementing changes and posting replies with commit references. Use when addressing PR reviews or responding to reviewer feedback. Follow the user's writing voice and prose style guides for reply text.
documentation5
github-pr-stack-convention
Stacked PR lifecycle: creating, retargeting, rebasing and merging PRs that depend on other PRs. Use when working with PRs based on other PRs or rebasing branches that have dependents. Pairs with github-pr-merge-convention for general merge strategy.
data-ai5
git-rebase-convention
Resolving rebase conflicts with design intent preservation. Use when rebasing, resolving merge conflicts or choosing a conflict resolution strategy.
content-media5
planning-dev-format
Plan structure for code implementation work. Context, interfaces, data flow and behaviours without writing the implementation itself. Use during plan_mode when the work involves building or modifying code. Pairs with planning-guide for the overall planning methodology.
development5
comment-format
Conventional Comments structure for review feedback. Labels, decorations and tone. Use when writing review comments, giving code feedback or posting PR review observations. Pairs with code-review-standard for what to evaluate. Follow the user's writing voice and prose style guides for comment text.
development5
pr-workflow-stack-judge-output
Output contract for stack-wide judge subagents in pr-workflow. The JSON shape with per-PR and cross-PR findings, attribution fields, optional self-signal, membership rules, and the verify_output self-check protocol. Loaded into each stack-judge subagent via --skill.
testing5
pr-workflow-stack-review-output
Output contract for stack-wide reviewer subagents in pr-workflow. The JSON shape with per-PR and cross-PR findings, perPr key rules, cross-PR span fields, and the verify_output self-check protocol. Loaded into each stack-review reviewer subagent via --skill.
testing5
pr-workflow-critique-output
Output contract for round-3 critique reviewer subagents in pr-workflow. The JSON shape of critique entries, position vocabulary, rationale requirements, and the verify_output self-check protocol. Loaded into each critique reviewer subagent via --skill.
testing5
code-tdd-guide
Test-driven development methodology. Red-green-refactor cycle, when to stub, how to validate failure reasons, commit cadence. Use when implementing with TDD, writing tests first or driving the tdd_loop tool.
tools5
github-issue-format
Issue body structure and narrative. The closed three-section body (Situation, Outcome, Acceptance), URI indexing and title conventions. Use when writing or editing a GitHub issue. Pairs with github-cli-convention for command syntax and markdown-standard for markdown structure. Follow the user's writing voice and prose style guides for issue text.
tools5
code-style-standard
Code design and style rules applied to all code. Readability, naming, structure, abstraction, testing and domain-driven design. Use when writing, modifying or reviewing code in any language. Follow the user's writing voice and prose style guides for code comments and doc comments.
development5
github-pr-review-guide
Pull request review workflow. Context gathering, code analysis and structured review posting. Use when reviewing someone else's PR. Pairs with code-review-standard for evaluation criteria and comment-format for comment structure. Follow the user's writing voice and prose style guides for review text.
development5
commit-format
Conventional commit message structure: types, scopes, subject and body rules. Use when writing a commit message or amending a commit. Pairs with git-cli-convention for command syntax and git-commit-convention for when to commit. Follow the user's writing voice and prose style guides for body text.
tools5
google-workspace-guide
Access Google Workspace (Gmail, Calendar, Drive, Docs, Sheets, Slides). Use when asked to "check email", "read inbox", "get calendar", "what's on my schedule", "find in drive", "search drive", "read doc", "open spreadsheet", "show slides", "list emails", "emails from [person]", "send email", "reply to", "schedule meeting", "create event", "cancel meeting", or any query about the user's Google account data. Handles email, calendar, documents, and files.
development5
pr-workflow-council-output
Output contract for round-1 council reviewer subagents in pr-workflow. The JSON shape of findings, location kinds, thread-relation fields, and the verify_output self-check protocol. Loaded into each reviewer subagent via --skill.
testing5
pr-workflow-judge-output
Output contract for round-2 judge subagents in pr-workflow. The JSON shape of consolidated findings, attribution fields, the optional self-signal, and the verify_output self-check protocol. Loaded into each judge subagent via --skill.
testing5
git-cli-convention
Command syntax for git operations. Heredoc format for commit messages, shell quoting and multi-line input patterns. Use when running git commit, git tag or any git command with structured input.
tools5
git-branch-convention
Branch naming, creation and safe transitions. Use when creating a branch, switching branches, moving commits between branches or starting new work.
tools5
markdown-standard
Markdown structure rules: Title Case headings with their exceptions, the line-width target and its legitimate exceptions, reference-style links, fenced code blocks with language tags, tables and lists. Use when writing or editing any markdown file (README, AGENTS, docs, plans, skill files), or when adding a heading, link, table or code block. Owns markdown structure; pairs with prose-standard, which owns voice, grammar, spelling and punctuation.
development5
quest-convention
Operational conventions for the quest system: when to use a quest versus a subquest versus a sidequest, when to scaffold a plan or research document, how to reorder priorities, when to add optional sections, when to conclude versus retire, the resuscitate pattern. Use when driving the quest tool, deciding kind, promoting or parking work, or organising a project as quests. Pairs with quest-format for the on-disk shape.
tools5
convention-recurrence-sensor-guide
How to measure whether convention corrections keep recurring in the pi session logs, by category and by week. Use to record a baseline before the convention gates take effect and to re-run afterwards to confirm the recurring categories bend down. Pairs with the convention gates (pr-guardian, issue-guardian, commit-guardian, slack-integration) and the convention-context extension.
tools5
prose-standard
Voice and style rules for all written output. Spelling (Canadian English), punctuation, tone and sentence structure. Use when writing or editing commit messages, PR descriptions, issue bodies, review comments, code comments, markdown, skill files, agent instructions or any other prose for humans or language models.
development5
pr-workflow-guide
How to drive the `pr_workflow` tool: a conversation-first PR review system with multi-model council pipeline (fan- out reviewers, judge consolidation, optional critique, user synthesis) and posting to GitHub. Use when the user asks to "review PR N", "run a council review", "look at this PR", "post a review", or any request to read or comment on a pull request. Pairs with code-review-standard for evaluation criteria, comment-format for comment shape, and prose-standard for written voice.
tools5
quest-format
Structure of a quest README and the documents that live under it: frontmatter shape, the four core and four optional body sections, emoji glyphs, ID format, alias notation, Cast bullets and Journey entries. Use when writing or editing a quest README, a plan, research, brief or report document under a quest. Pairs with quest-convention for choices like kind, promotion and reordering. Follow the prose-standard for voice.
development5
github-cli-convention
Command syntax for GitHub CLI operations. Heredoc format for PR and issue bodies, title conventions and metadata flags. Use when running gh pr create, gh issue create or any gh command with structured input.
tools5
github-pr-format
PR description structure and narrative. The closed three-section body (Situation, Resolution, Validation), URI indexing, self-review guidance and title conventions. Use when writing or editing a pull request description. Pairs with github-cli-convention for command syntax and markdown-standard for markdown structure. Follow the user's writing voice and prose style guides for description text.
tools5
subagent-fleet-guide
How to drive the `subagent` tool: spawn N pi processes concurrently for persona sweeps (security/performance/ readability of the same artifact), multi-angle investigation (data flow vs lifecycle vs config of the same bug), or fleet brainstorming (N answers from N models). Use when the user asks to "examine from various angles", "get multiple perspectives", "fan out across personas", "parallel investigation", "have N models try this", or any request that benefits from divergent independent passes. Pairs with prose-standard for written voice and any domain skills the personas should inherit.
tools5
code-review-standard
Evaluation criteria for code review: test quality, implementation quality, naming, consistency, scope and PR descriptions. Use when reviewing code or a pull request. Pairs with comment-format for review comment structure.
development5
planning-guide
The single planning skill: how to plan collaboratively and how to structure the living plan document. Covers the staged plan workflow (think, draft, build), debating before deciding, the front-matter contract, the recommended sections, checkbox progress and deviation. Use when planning, designing before building, driving the plan tool, or writing a plan file. Works for code, investigation, writing and ops plans alike. Follow the user's prose standard for any text in the plan.
tools5
slack-guide
Access Slack: search messages, read threads, send messages, send threads, edit messages, upload files, look up users and channels, manage reactions. Use when asked to "check Slack", "find messages", "search Slack", "send a message", "post a thread", "send these as a thread", "edit that message", "fix that message", "update what I said", "upload a file", "share this file", "attach this", "what did X say", "show me the thread", "who is", "react to", or any query about Slack messages, channels or users.
development5
extension-dev-guide
How to develop Pi extensions. Discovery workflow for TUI components, available APIs, composition patterns and common mistakes. Use when building or modifying extensions.
tools4
github-project-guide
Managing items in GitHub Projects v2. Query project items, reorder them, and resolve project IDs. Use when working with GitHub project boards or reordering items in a project.
documentation4
taxonomy-guide
Naming taxonomy for skills and extensions in this package. Domains, type suffixes, location rules and the decision framework for when to create a new skill, extension or add to AGENTS.md. Use when creating, renaming or reorganizing skills and extensions.
tools4
session-log-guide
Pi session log format and extraction patterns. How to find session files, parse the JSONL structure, and extract user messages, tool calls, and errors. Use when analyzing past pi sessions or debugging session behaviour.
tools4
extension-keybinding-guide
Keybinding system for Pi extensions. Rules, verb set, footer layout and conventions for panels, gates and interactive prompts. Use when writing or modifying extensions that have user-facing UI.
tools4
github-sub-issue-guide
Managing sub-issues in GitHub Issues. Query, reorder, and create sub-issues using the GraphQL API. Use when working with parent/child issue relationships or reordering sub-issues within an epic.
development4