Skills creating-issues

📦

creating-issues

Name: creating-issues
Author: C0ntr0lledCha0s

v1.0.0 Content revision r2 Safe ⚙️ External commands🌐 Network access📁 Filesystem access

Create Consistent GitHub Issues

Poorly structured issues create ambiguity and require manual cleanup. This skill drafts and validates titles, bodies, labels, milestones, projects, and relationships.

Supports: Claude Codex Code(CC)

🥇 84 Gold

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "creating-issues" from https://skillstore.io/skills/c0ntr0lledcha0s-creating-issues.md and its manifest at https://skillstore.io/api/skills/c0ntr0lledcha0s-creating-issues/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/c0ntr0lledcha0s-creating-issues.md Signed manifest GET /api/skills/c0ntr0lledcha0s-creating-issues/manifest Signed lockfile GET /api/skills/c0ntr0lledcha0s-creating-issues/lockfile

Test it

Using "creating-issues". Review the title: [FEATURE] Add dark mode

Expected outcome:

Suggested title: Add dark mode support
Type: feature
Priority: priority:medium
Scope: confirm the affected interface component before creation

Using "creating-issues". Draft an issue for login failures with special characters.

Expected outcome:

Summary: Fix authentication failures for passwords containing supported special characters.
Acceptance criteria cover successful login, specific validation errors, regression tests, and unchanged standard login behavior.
Recommended labels: bug, priority:high, and the repository authentication scope.

Using "creating-issues". Plan issues for a new authentication system.

Expected outcome:

Create one parent feature issue describing the authentication outcome and shared constraints.
Create child issues for storage, API endpoints, interface changes, tests, and documentation.
Confirm project, milestone, priorities, scopes, and blockers before creating any issue.

Security Audit

Safe

v10 • 7/23/2026 Open versioned report

Review found one medium-risk temporary-file pattern and no malicious or deceptive intent. The predictable /tmp issue body can be replaced or symlinked before GitHub CLI reads it. Remaining alerts are Markdown backticks, fixed argument-list subprocess calls, validation output, or intentional GitHub metadata queries.

Files scanned

2,217

Lines analyzed

Review items

False positives ignored

Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

SKILL.md:439

Temp directory access

--body-file /tmp/issue-body.md

The example uses a predictable file in shared /tmp. Another local process could replace or symlink it before GitHub CLI publishes the body.

Risk Factors

⚙️ External commands (50)

references/label-conventions.md:219 scripts/detect-scope.py:39 scripts/issue-helpers.py:22 scripts/issue-helpers.py:78 scripts/issue-helpers.py:80 SKILL.md:29 SKILL.md:38 SKILL.md:39 SKILL.md:40 SKILL.md:41 SKILL.md:42 SKILL.md:45-47 SKILL.md:47-52 SKILL.md:52 SKILL.md:53 SKILL.md:54-57 SKILL.md:57 SKILL.md:62-63 SKILL.md:63-68 SKILL.md:68 SKILL.md:69 SKILL.md:70-73 SKILL.md:73-89 SKILL.md:89-100 SKILL.md:100-101 SKILL.md:101-102 SKILL.md:102-103 SKILL.md:103-104 SKILL.md:104-105 SKILL.md:105-108 SKILL.md:108-109 SKILL.md:109-110 SKILL.md:110-111 SKILL.md:111-118 SKILL.md:118-132 SKILL.md:132-135 SKILL.md:135-164 SKILL.md:164-167 SKILL.md:167-190 SKILL.md:190-200 SKILL.md:200-201 SKILL.md:201-202 SKILL.md:202-203 SKILL.md:203-209 SKILL.md:209-211 SKILL.md:211-213 SKILL.md:213-217 SKILL.md:217-220 SKILL.md:220-224 SKILL.md:224-227

🌐 Network access (1)

scripts/issue-helpers.py:32

📁 Filesystem access (1)

SKILL.md:439

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/c0ntr0lledcha0s-creating-issues/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/c0ntr0lledcha0s-creating-issues/security.svg)](https://skillstore.io/skills/c0ntr0lledcha0s-creating-issues?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/c0ntr0lledcha0s-creating-issues?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/c0ntr0lledcha0s-creating-issues/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/c0ntr0lledcha0s-creating-issues.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

C0ntr0lledCha0s. (2026). creating-issues security audit report (audit version 10) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/c0ntr0lledcha0s-creating-issues/audits/10

BibTeX citation

@techreport{c0ntr0lledcha0s-c0ntr0lledcha0s-creating-issues-2026,
  author = {C0ntr0lledCha0s},
  title = {creating-issues security audit report (audit version 10)},
  institution = {Skillstore},
  year = {2026},
  number = {10},
  url = {https://skillstore.io/skills/c0ntr0lledcha0s-creating-issues/audits/10},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "creating-issues security audit report (audit version 10)"
version: "1.0.0"
type: report
authors:
  - name: "C0ntr0lledCha0s"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/c0ntr0lledcha0s-creating-issues/audits/10"
identifiers:
  - type: other
    value: "skillstore:c0ntr0lledcha0s-creating-issues:audit:10"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Document a Reproducible Bug

Turn a bug report into a complete issue with reproduction steps, expected behavior, acceptance criteria, and labels.

Standardize Repository Work

Validate titles and select consistent type, priority, and scope labels for incoming work.

Plan a Release

Prepare related issues with milestones, project placement, dependencies, and parent-child structure.

Try These Prompts

Improve an Issue Title

Review this issue title: "[BUG] Login fails". Suggest an imperative title without a type prefix and explain the change.

Draft a Bug Report

Draft a bug issue for {problem}. Include reproduction steps, expected behavior, actual behavior, acceptance criteria, environment details, and recommended labels.

Prepare a Feature Issue

Create a feature issue plan for {capability}. Propose the title, body, type, priority, scope, milestone, and project placement. Ask before creation.

Design an Issue Hierarchy

Analyze {work_items} and design a parent-child issue structure. Identify blockers and related work, then prepare complete issue content and GitHub metadata.

Best Practices

Confirm scope, priority, milestone, project placement, and relationships before creating external issues.
Use one primary type label, one priority label, and at least one specific scope label.
Verify created issues, project items, and relationships immediately after each external update.

Avoid

Do not place type prefixes in titles when labels already express the issue type.
Do not create issues with vague summaries or acceptance criteria that cannot be tested.
Do not use task lists as a substitute for GitHub parent-child relationships.