菜单
Automates pull request creation with branch management, code formatting, and integration with professional-commit-workflow. Supports GitHub CLI, automated PR descriptions, and project-specific formatters (Biome, Black, Prettier).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Browser automation with a persistent session, driven by the Playwright Python API. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/core:ponytail-audit". One-shot report, does not apply fixes.
Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/core:ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /core:ponytail-review. Complements correctness-focused review, this one only hunts complexity.
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.
Ingests a new source (web clipping, AI chat export, raw note, transcript) into an Obsidian-based LLM knowledge wiki. Files the source under _raw/, distills it into one or more _wiki/ pages, updates index and log, and pulls bidirectional cross-references. Triggers when the user asks to "ingest this source", "digest this clipping into the wiki", or runs /wiki:ingest while working in a configured wiki vault.
| name | professional-pr-workflow |
| description | Automates pull request creation with branch management, code formatting, and integration with professional-commit-workflow. Supports GitHub CLI, automated PR descriptions, and project-specific formatters (Biome, Black, Prettier). |
Automates the complete pull request workflow: branch creation, code formatting, commit integration, and PR creation via GitHub CLI.
Features:
Required:
gh) - installed and authenticatedOptional (for code formatting):
Check branch status:
Commit changes:
professional-commit-workflowFormat code (optional, skip with --no-format)
Create PR:
gh pr create# Standard PR workflow
python scripts/main.py
# Draft PR
python scripts/main.py --draft
# Without formatting
python scripts/main.py --no-format
# Single commit (all changes in one)
python scripts/main.py --single-commit
# Change target branch
python scripts/main.py --target develop
biome format --write .prettier --write .eslint --fix .black .isort .ruff format .markdownlint --fix **/*.mdmdformat .============================================================
Professional PR Workflow
============================================================
Branch status: main (protected)
New branch created: feature/user-dashboard-2024-12-21
Code formatting:
Biome: 5 files formatted
ESLint: 0 errors
Branch pushed: origin/feature/user-dashboard-2024-12-21
PR created: #42
https://github.com/user/repo/pull/42
PR workflow completed successfully
{
"protected_branches": ["main", "master", "develop"],
"default_target": "main",
"auto_delete_branch": false,
"formatters": {
"javascript": "biome",
"python": "black",
"java": "google-java-format"
}
}
Branch errors: Checks existing branches, offers alternative names
Format errors: Shows details, enables --no-format fallback
GitHub CLI errors: Checks authentication, shows gh setup instructions
Push errors: Retry logic, manual push commands