Menu
Open an issue on GitHub. Use when the user asks to file/open/draft/create an issue. Useful for bug reports, pipeline failures, feature requests, etc.
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
Triage issues labeled 'untriaged' in a repository. Investigates each issue, correlates with recent activity, and categorizes into: customer issue, ready for work, needs investigation, or already addressed. Informational only — does not modify issues.
Open a pull request on GitHub. Use when the user asks to open or create a pull request on GitHub.
Write property-based tests in C# using CsCheck. Covers generator composition, property selection (round-trip, invariant, model-based, metamorphic), parallel linearizability testing, performance comparison, classification, and configuration. Use when writing, reviewing, or improving property-based tests in a .NET project that uses CsCheck.
| name | creating-issues |
| description | Open an issue on GitHub. Use when the user asks to file/open/draft/create an issue. Useful for bug reports, pipeline failures, feature requests, etc. |
gh issue create --repo <owner/repo> --title "<title>" --body "<body>".Write issues in a direct, actionable style:
Validate signatures before publishing images.Currently, ..., The <workflow> is failing ..., or I like <tool>, and it would be easier if ....This means ..., That does not satisfy ..., or The <label/setting> is only added when ....We should ..., Instead, ..., or This would ....Use this style for broken behavior, CI failures, regressions, automation bugs, and usability failures.
<Current behavior or symptom in one sentence.>
<Evidence link, screenshot, code link, or failing run.>
```text
<Exact error text, if available.>
```
<Brief root cause or why this is actionable, if known.>
<Expected behavior or requested fix.>
Notes:
Use this style for enhancements, workflow improvements, distribution requests, validation hardening, and policy changes.
<Motivation or current limitation in one short paragraph.>
<Proposed change using "We should ..." or "Instead, ...".>
<Concrete examples, commands, configuration, or implementation direction.>
<Constraints, tradeoffs, or rollout notes, if relevant.>
Notes:
Bug/failure report
The `check-markdown-links` workflow is failing during action setup before link checking runs.
Failure from PR #7175: https://github.com/example/repo/actions/runs/123/job/456
```text
The action example/action@sha is not allowed because all actions must match the allowed-actions policy.
```
The workflow uses `example/action@v1`, which attempts to fetch `example/action` by SHA. That does not satisfy the current allowed-actions policy, so the workflow cannot run successfully.
Feature request
Currently, every failure creates a new GitHub issue. If the same failure occurs repeatedly, duplicate issues accumulate.
Instead, `NotificationService` should detect an existing open issue for the same failure and update it rather than opening a new one.
A deduplication key, such as subscription name or manifest/repo, could be added to the notification metadata.