원클릭으로
pi-agent
pi-agent에는 szokeasaurusrex에서 수집한 skills 14개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.
이 저장소의 skills
Write plans intended for a cheaper or less capable implementation model. Use when the user asks for a plan suitable for another LLM, junior engineer, intern, cheaper model, coding agent, or implementation delegate.
Use when the user asks for ideas, brainstorming, discussion, exploration, possibilities, pros and cons, tradeoffs, or to "think through" something.
Use this skill when asked to plan something, or plan and implement. Do not use when asked to implement a plan.
Use when initializing Rust projects or modifying Cargo.toml, Cargo.lock, cargo config, or other cargo-related files. Prefer this skill for dependency changes, features, package metadata, workspaces, and cargo commands. Do not load it for editing Rust source code generally.
Split an existing commit or PR into smaller reviewable pieces through a one-hunk patch queue. Use when extracting part of a commit, splitting a commit into multiple commits, or splitting PR changes from one or more source commits without starting from direct source edits.
Checkpoint, inspect, and return through session tree branches. Use when exploring uncertain approaches, investigating code, or when the user asks for a forked agent.
Use multiple pi sub-agents for delegation, isolation, and parallel work. Use when tasks can be split and later merged.
Use when drafting or editing persisted technical writing artifacts such as commit messages, issue bodies, PR descriptions, documentation comments, or documentation files.
Use when creating or updating agent skills (`skills/<name>/SKILL.md` files).
Use this skill when asked to create or amend a commit.
Create a GitHub repo as repo/.bare with repo/<branch> worktrees and origin-tracking branches. Use when users ask for bare+worktree layout.
Use when asked to create or draft GitHub issues. Do not use when asked only to "plan" issues.
Use whenever fetching documentation from docs.sentry.io or develop.sentry.dev.
Use GitHub CLI (`gh`) for all GitHub interactions. Prefer built-in `gh` commands; use `gh api` only when needed.