333-333-333/github-issues
skills/github-issues/SKILL.md
Create GitHub issues in Spanish following project conventions: structured sections, conventional title prefixes, and consistent labeling. Trigger: When creating GitHub issues, reporting bugs, or proposing features via gh CLI.
tools
Updated Mar 25, 2026
$ install --global
skillsauthnpx skillsauth add 333-333-333/agents github-issuesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 25, 2026, 12:15 PM44.6s3 files scanned
SKILL.md
- name:
- github-issues
- description:
- >
- Create GitHub issues in Spanish following project conventions:
- structured sections, conventional title prefixes, and consistent labeling.
- Trigger:
- When creating GitHub issues, reporting bugs, or proposing features via gh CLI.
- license:
- Apache-2.0
- author:
- 333-333-333
- version:
- 1.0
- type:
- generic
- scope:
- [root]
When to Use
- Creating a new GitHub issue (feature, bug, chore, etc.)
- Reporting a bug found during development or CI
- Proposing a feature or enhancement for discussion
Critical Patterns
Language
All issue titles and bodies MUST be written in Spanish (Chile). Code references, file paths, and technical terms may remain in English.
Title Format
Issue titles follow conventional-commit style prefixes:
| Type | When | Example |
|------|------|---------|
| feat: | New functionality | feat: publicar artefactos de contenedor desde main |
| feat(scope): | Scoped feature | feat(ci): pipeline de despliegue a Cloud Run |
| fix: | Bug report | fix: webhook de Discord falla con error 'sender is required' |
| chore: | Maintenance | chore: actualizar dependencias de Node |
| docs: | Documentation | docs: agregar guía de contribución |
| refactor: | Code improvement | refactor: extraer lógica de validación |
Body Structure
Use the appropriate template based on issue type:
- Features / enhancements: Contexto, Propuesta, Alcance, Criterios de aceptación
- Bugs: Descripción, Causa raíz, Pasos para reproducir, Solución propuesta, Referencias
See assets/issue-template-feat.md for the feature template.
See assets/issue-template-bug.md for the bug template.
Labels
Apply the most appropriate label from the repository's existing labels:
| Label | When |
|-------|------|
| enhancement | feat: issues |
| bug | fix: issues (bugs) |
| documentation | docs: issues |
Checklist Before Creating
- Title uses conventional-commit prefix
- Body is in Spanish
- Sections follow the appropriate template
- Label is applied
- Acceptance criteria are verifiable (checkboxes)
Commands
gh issue create --title "feat: ..." --label enhancement --body "$(cat <<'EOF' ... EOF)"
gh issue create --title "fix: ..." --label bug --body "$(cat <<'EOF' ... EOF)"
gh issue list --limit 10 # review existing issues for style
Resources
- Templates: See assets/ for issue body templates (feat, bug)
Related Skills
333-333-333/ux-review
testing
VerifiedTrustedCommunity
Review Flutter components and screens for UX/UI compliance. Trigger: When user invokes /ux-review command or requests UX audit.
SKILL.mdUpdated Mar 25, 2026
333-333-333/typescript
development
VerifiedTrustedCommunity
TypeScript strict patterns and best practices. Trigger: When implementing or refactoring TypeScript in .ts/.tsx (types, interfaces, generics, const maps, type guards, removing any, tightening unknown).
SKILL.mdUpdated Mar 25, 2026
333-333-333/testing-strategy
testing
VerifiedTrustedCommunity
Testing philosophy and strategy for every feature: test pyramid, mandatory levels per change type, completion checklist, and skill delegation. Trigger: When planning tests for a feature, reviewing test coverage, defining acceptance criteria, or asking what tests a change needs.
SKILL.mdUpdated Mar 25, 2026
333-333-333/terraform-security
development
VerifiedTrustedCommunity
Terraform security practices: sensitive variables, secret management, state protection, .gitignore patterns, and CI/CD credential handling. Trigger: When handling secrets in Terraform, configuring state backends, reviewing .gitignore for Terraform, or setting up CI/CD pipelines for infrastructure.
SKILL.mdUpdated Mar 25, 2026