Menú
Git workflow guidance for commits, branches, and pull requests
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Updating all tailrelay documentation — README, CHANGELOG, release notes, AGENTS.md, SKILL.md files, webui/README.md, UI screenshots, and the Docusaurus docs site. Use when adding user-facing features, releasing a new version, updating component versions, or when any doc's reviewed_at SHA is out of date with HEAD.
Security and privacy review for tailrelay — dependency CVE scanning, Go module auditing, auth review, and code-level vulnerability checks. Use when reviewing code for security issues, auditing Dockerfile dependencies, checking for secrets/injection risks, or assessing privacy of logged/persisted data.
tailscale serve and funnel relay management — HTTPS, TCP, and Funnel relay types, serve_relays.json format, reconciliation flow, API endpoints, migration from legacy caddy/socat configs, ErrTailscaleNotReady and ErrFunnelNotAllowed handling. Use when working with internal/serve/, handlers/serve.go, or /api/serve/* endpoints.
Tailscale VPN daemon management, CLI integration, authentication, and networking for the tailrelay container. Use when working with Tailscale configuration, login flows, device authentication, MagicDNS, HTTPS certificates, or network connectivity issues.
Writing tests and CI/CD for tailrelay — Go unit tests, Python integration tests, CI pipeline jobs, and test infrastructure. Use when adding new tests, extending the integration suite, modifying ci.yml, or improving test coverage for any Go package or the container behaviour.
Go Web UI application development — handlers, authentication, backup, frontend SPA, build workflow, and testing. Use when working with the webui/ directory, Go code, frontend assets, HTML templates, the SPA build system, or any Web UI feature development.
| name | git-workflow |
| description | Git workflow guidance for commits, branches, and pull requests |
| license | Apache-2.0 |
| metadata | {"version":"1.0.0","author":"agno-team","tags":["git","version-control","workflow"]} |
You are a Git workflow assistant. Help users with commits, branches, and pull requests following best practices.
For commit message generation and validation, use get_skill_script("git-workflow", "commit_message.py").
<type>(<scope>): <subject>
- <unique change description>
- <another unique change description>
<footer>
feat(auth): add oauth2 login support
- implement `OAuth2` authentication flow with google and github providers
- add token refresh mechanism and session management
closes #123
fix(api): handle null response from external service
- add null check before processing response data
- prevent `NullPointerException` when external service returns empty response
fixes #456
<type>/<ticket-id>-<short-description>
feature/AUTH-123-oauth-loginfix/BUG-456-null-pointerchore/TECH-789-update-depsFollow commit message format for the title.
## Summary
Brief description of what this PR does.
## Changes
- Change 1
- Change 2
## Testing
How was this tested?
## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No breaking changes
git checkout main
git pull origin main
git checkout -b feature/TICKET-123-description
git add -p # Interactive staging
git commit -m "type(scope): description"
git fetch origin
git rebase origin/main
git push -u origin feature/TICKET-123-description
# Then create PR on GitHub/GitLab