القائمة
Manage GitHub sub-issues using the gh-sub-issue extension. Use when the user asks to create, list, add, or remove sub-issues (child issues) from a parent issue.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when observing server-side state of a Shiny for Python (py-shiny) app - inspecting reactive/calc values in a running session, capturing current input/output state, exposing internal values to a test harness, asserting server-side values in snapshot tests, or when tempted to add print statements or hidden outputs to see server-side values. (For writing Playwright end-to-end tests against the rendered UI, use the testing skill.)
Use when writing or running end-to-end tests for a Shiny for Python (py-shiny) app - launching an app under pytest, locating and asserting on UI components (inputs, outputs, cards, navsets), simulating user interaction with Playwright, or when tempted to hand-roll CSS selectors, raw Playwright locators, or sleep() waits against Shiny-rendered HTML.
Use when adding observability to a Shiny for Python (py-shiny) app with OpenTelemetry - tracing reactive execution, profiling slow outputs or update cycles, monitoring sessions in production, exporting spans to a backend (Jaeger, Logfire, Honeycomb, Datadog, OTLP), suppressing telemetry for sensitive code, or when tempted to call trace.set_tracer_provider() inside app code to set up instrumentation.
Use when a Shiny for Python (py-shiny) app needs to save and restore its state - shareable URLs that reproduce the current inputs, restoring state after a page refresh, persisting session state to the server, excluding inputs from saved state, or when tempted to hand-roll query-string parsing or a custom persistence layer to remember input values.
Walk through the full Shiny for Python release train interactively, phase by phase. Use when the user says "release", "start a release", "py-shiny release", "release train", or wants to publish new versions of py-shiny and its ecosystem packages (py-htmltools, py-shinyswatch, py-shinywidgets, shinylive, py-shinylive, r-shinylive). Guides through version bumps, CI checks, tagging, PyPI publishing, conda-forge, Huggingface, site updates, and blog post publication.
Comprehensive guide for porting UI components from R's bslib package to py-shiny. Use this skill when: (1) User asks to "port this feature" or "port a component" and mentions bslib or links to a bslib PR (e.g., github.com/rstudio/bslib/pull/...), (2) Porting a new component from bslib to py-shiny, (3) Adding a new input, output, or UI component that exists in bslib, (4) Implementing feature parity with bslib, (5) Working on bslib-related features or components. Covers the complete workflow including understanding source implementation, creating Python equivalents, vendoring assets (SCSS, CSS, JavaScript), creating tests, documentation, and all necessary project files.
استنادا إلى تصنيف SOC المهني
| name | sub-issue |
| description | Manage GitHub sub-issues using the gh-sub-issue extension. Use when the user asks to create, list, add, or remove sub-issues (child issues) from a parent issue. |
Manage GitHub sub-issues (child issues) using the gh sub-issue extension.
Before using any sub-issue commands, check if the extension is installed:
gh extension list | grep -q sub-issue || gh extension install yahsan2/gh-sub-issue
This will install the extension if it's not already present.
Create a new issue directly linked as a child of a parent issue:
gh sub-issue create --parent <parent-issue> --title "<title>" --body "<body>" --repo posit-dev/connect
Flags:
-p, --parent — Parent issue number or URL (required)-t, --title — Title for new sub-issue (required)-b, --body — Body text for the sub-issue-l, --label — Comma-separated labels-a, --assignee — Comma-separated usernames-m, --milestone — Milestone name or number--project — Projects (can specify multiple times)gh sub-issue add <parent-issue> <sub-issue> --repo posit-dev/connect
gh sub-issue list <parent-issue> --repo posit-dev/connect
gh sub-issue list <parent-issue> --state all --repo posit-dev/connect
gh sub-issue remove <parent-issue> <sub-issue> --repo posit-dev/connect
--repo posit-dev/connect to ensure correct repository context--body with heredoc for multi-line descriptions:gh sub-issue create --parent 123 --title "My issue" --body "$(cat <<'EOF'
Description here.
**Acceptance criteria:**
1. First item
2. Second item
EOF
)" --repo posit-dev/connect