Install
$ agentstack add skill-ai-driven-dev-framework-04-issue-create ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Issue Create
Files well-formed issues in the configured tracker after gathering enough context to be actionable.
Available actions
| # | Action | Role | Input | | --- | --------------- | -------------------------------------------------------------------------- | -------------------------------------- | | 01 | issue-create | Detect tool, fill template, validate, open the issue | problem_description, labels, type |
Default flow
Single action skill. The router dispatches to issue-create whenever an issue or bug-report phrase appears.
Transversal rules
- Detect the ticketing tool from project memory first, then fall back to inspecting
git remote get-url origin. - Tool-agnostic: invoke whichever ticketing tool is configured for the project.
- Always wait for explicit user approval of title, body, labels, type, projects, and milestones before creating.
- Issue body follows
@assets/issue-template.md. - Be thorough and concise. Short sentences. Focus on clarity, reproduction steps, and expected behavior.
- Read
@assets/CONTRIBUTING.mdfor project-specific issue rules before drafting.
References
- None.
Assets
@assets/issue-template.md: Issue / ticket body template.@assets/CONTRIBUTING.md: Contribution guidelines, including issue process.
External data
- None.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ai-driven-dev
- Source: ai-driven-dev/framework
- License: MIT
- Homepage: https://www.ai-driven-dev.fr/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.