managing-relationships
Manage GitHub Issue Relationships
GitHub issue hierarchies are difficult to manage with the standard issue CLI. This skill uses GraphQL helpers to create, inspect, and verify relationships.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "managing-relationships" from https://skillstore.io/skills/c0ntr0lledcha0s-managing-relationships.md and its manifest at https://skillstore.io/api/skills/c0ntr0lledcha0s-managing-relationships/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.
Test it
Using "managing-relationships". Show the parent for issue #68.
Expected outcome:
Issue #68 has parent #67, "Platform migration." No changes were made.
Using "managing-relationships". Add issue #68 under issue #67 after confirmation.
Expected outcome:
- Confirmed repository owner/project and the requested parent-child change.
- Added issue #68 as a sub-issue of issue #67.
- Verified that issue #68 now appears under issue #67.
Using "managing-relationships". Review dependencies for issue #90.
Expected outcome:
- Issue #90 is blocked by open issues #84 and #87.
- Issue #90 blocks issue #95.
- Resolve issue #84 first because it also blocks issue #87.
Security Audit
Medium RiskThe subprocess calls use fixed argument arrays without shell execution, and the Markdown detections are formatting rather than executable backticks. The skill can change authenticated GitHub relationships without an explicit confirmation requirement.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (50)
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.
Copy report link
https://skillstore.io/skills/c0ntr0lledcha0s-managing-relationships/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/c0ntr0lledcha0s-managing-relationships?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/c0ntr0lledcha0s-managing-relationships?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/c0ntr0lledcha0s-managing-relationships/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/c0ntr0lledcha0s-managing-relationships.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). managing-relationships security audit report (audit version 9) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/c0ntr0lledcha0s-managing-relationships/audits/9BibTeX citation
@techreport{c0ntr0lledcha0s-c0ntr0lledcha0s-managing-relationships-2026,
author = {C0ntr0lledCha0s},
title = {managing-relationships security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/c0ntr0lledcha0s-managing-relationships/audits/9},
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: "managing-relationships security audit report (audit version 9)"
version: "1.0.0"
type: report
authors:
- name: "C0ntr0lledCha0s"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/c0ntr0lledcha0s-managing-relationships/audits/9"
identifiers:
- type: other
value: "skillstore:c0ntr0lledcha0s-managing-relationships:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Build an issue hierarchy
Connect existing epics, features, and tasks as parent and sub-issues, then verify the resulting structure.
Audit repository relationships
Inspect parents, children, blockers, and tracking links before reorganizing an active backlog.
Review release blockers
List blocking and blocked-by relationships to identify unresolved work affecting a release.
Try These Prompts
Show all relationships for issue #42 in the current repository. Do not change anything.
Add issues #43 and #44 under #42. Confirm the repository and planned changes before execution, then verify the result.
Make #100 parent of #101 and #102, then make #101 parent of #103. Check current parents, request confirmation, apply, and verify.
Analyze dependencies for issues #200 through #210. Identify open blockers, hierarchy gaps, and conflicting parents. Return a prioritized plan without modifying GitHub.
Best Practices
- Inspect current parents and relationships before making changes.
- Confirm the repository and issue numbers before every mutation.
- Verify the resulting hierarchy after each operation.
Avoid
- Do not replace an existing parent without explicit approval.
- Do not treat task-list links as true sub-issue relationships.
- Do not create deep hierarchies that are difficult to navigate.
Frequently Asked Questions
What authentication does this skill require?
Can it create new GitHub issues?
Can one issue have multiple parents?
Can it modify blocking dependencies?
Does it work across repositories?
How does it avoid unintended changes?
Developer Details
Author
C0ntr0lledCha0sLicense
MIT
Author version
v1.0.0
Skillstore revision
r2
Ref
a39a91716eadede5f4cdefd78178fed4e837a128
Maintenance freshness
7/24/2026
Usage
7 downloads · 192 views
File structure