tritonkit-dev-feedback

Collects TritonKit adoption feedback and files redacted GitHub issues with evidence.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-dev-feedback-neptunekit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tritonkit-dev-feedback
Source: https://github.com/NeptuneKit/TritonKit/tree/main/TritonKit.skills/tritonkit-dev-feedback
Command: npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-dev-feedback-neptunekit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When developers try, adopt, or integrate TritonKit during its active development stage, bugs, missing capabilities, confusing behavior, and documentation gaps often go unreported or are filed without enough evidence. This Skill turns those findings into well-structured, redacted GitHub issues in NeptuneKit/TritonKit, with the AI agent owning the filing action instead of asking the user to do it. ## Core Features & Use Cases - Guided issue filing: Classifies feedback as bug, feature, docs, or question, checks for duplicates, applies a standard body template, and runs a mandatory redaction preflight before any gh issue create or gh issue edit. - Evidence collection routing: Directs the agent to the right reference for iOS embedded runtime evidence, host-side simulator/emulator evidence (iOS, Android, HarmonyOS, Web), or CLI schema and contract feedback, always preferring machine-readable triton ... --json output. - Integration guidance: Provides SwiftPM/CocoaPods Debug-only iOS integration steps and HarmonyOS host-side and embedded SDK validation workflows. - Use Case: A user reports that triton act tap fails on a UICollectionViewCell. The agent reproduces it with Triton CLI commands, preserves the strategy and error code, redacts private bundle IDs and paths, and files a [Bug] issue with full reproduction evidence. ## Quick Start Ask the agent to use the tritonkit-dev-feedback skill to reproduce your TritonKit problem, collect sanitized evidence, and file a GitHub issue in NeptuneKit/TritonKit.

Frequently Asked Questions about tritonkit-dev-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I report a TritonKit bug as a GitHub issue?▼

Describe the problem to the agent, which reproduces it with triton CLI commands, collects sanitized evidence, runs a redaction preflight, and files the issue with gh issue create against NeptuneKit/TritonKit. You do not need to file it yourself when GitHub access is available.

How do I integrate TritonKit into an iOS app with SwiftPM or CocoaPods?▼

Add only the TritonKit product from https://github.com/NeptuneKit/TritonKit.git to your app target, and wrap bootstrap code in #if DEBUG with explicit opt-in. CocoaPods supports a Debug-only configuration; SwiftPM requires a separate Debug-only target or scheme to keep Release builds unlinked.

Does TritonKit support HarmonyOS and DevEco Emulator validation?▼

Yes, host-side validation works through the HDC adapter with triton device and app commands using --platform harmony, requiring no embedded runtime. Embedded SDK validation uses the lowercase tritonkit package and direct runtime-base-url checks while the SDK is standalone.

What evidence should I collect before filing a TritonKit CLI issue?▼

Run triton status, doctor, capabilities, schema, and plan with --json before falling back to raw xcrun, adb, or hdc. Preserve error codes, nextAction fields, and sanitized command output rather than attaching raw logs or unredacted evidence bundles.

What private data must be redacted before filing a public issue?▼

Remove app names, bundle IDs, team IDs, usernames, emails, phone numbers, internal hosts, absolute private paths, and unredacted screenshots or logs. The skill runs a mandatory regex-based preflight scan on the issue body file and treats any match as a stop condition before publishing.