Menu
Automate issue triage, planning, and branch creation for issue-driven development.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Data-first visualization design combining Tufte principles with Jobs/Ive simplicity for React + Nivo dashboards.
Automated agent workflow for reviewing and updating project agent context files when code changes are made.
Create a custom Dagster Component with demo mode support, realistic asset structure, and optional custom scaffolder using the dg CLI. Use this skill if there is no Component included in an existing integration or if Dagster does not have the integration.
Expert guidance for Dagster data orchestration including assets, resources, schedules, sensors, partitions, testing, and ETL patterns. Use when building or extending Dagster projects, writing assets, configuring automation, or integrating with dbt/dlt/Sling.
Expert guidance for working with Dagster and the dg CLI. ALWAYS use before doing any task that requires knowledge specific to Dagster, or that references assets, materialization, components, data tools or data pipelines. Common tasks may include creating a new project, adding new definitions, understanding the current project structure, answering general questions about the codebase (finding asset, schedule, sensor, component or job definitions), debugging issues, or providing deep information about a specific Dagster concept.
Initialize a dagster project using the create-dagster cli. Create a dagster project, uv virtual environment, and everything needed for a user to run dg dev or dg check defs successfully. (project)
| name | start-issue |
| description | Automate issue triage, planning, and branch creation for issue-driven development. |
| version | 1.0.0 |
| tags | ["github","workflow","planning"] |
Use this skill to go from GitHub issue → plan → branch in a consistent, repeatable way.
Load issue context
gh issue view <id> --json title,body,labels,assignees,comments,updatedAt to avoid project-card GraphQL issues.Clarify scope
Locate code
rg --files to identify modules.rg -n "<keyword>" to locate patterns.Plan
Create branch
git checkout -b feat/issue-<id>-<short-slug> (or fix/issue-<id>-<short-slug> for bugfixes).Post plan comment (optional)
gh issue comment <id> --body "...".Implement and validate
main.