Menu
GitHub Issues tracking workflow for droneroute. Use when managing tasks, features, and bugs.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
PR-based development workflow for droneroute. Use when implementing features, fixing bugs, or making any code changes. Covers branch creation, CI checks, changelog entries, and PR creation.
WCAG 2.1 AA accessibility patterns for droneroute — color contrast, ARIA, keyboard navigation, Leaflet map a11y, and Radix UI component checklist.
Playwright testing patterns for droneroute. Covers screenshot automation, test structure, and CI integration.
Security patterns for droneroute — JWT auth guards, input validation, SQL injection prevention, and environment variable safety.
Before/after screenshot workflow for UI PRs. Covers capture techniques, annotation, and embedding in PRs and changelogs.
| name | todo-tracking |
| description | GitHub Issues tracking workflow for droneroute. Use when managing tasks, features, and bugs. |
Ensure project work is tracked via GitHub Issues. All tasks, features, bugs, and improvements are managed as issues in the repository — there is no local TODO file.
Before starting any implementation work, run:
gh issue list
This gives you the current backlog and prevents duplicate work.
When a PR resolves an issue, include Fixes #N in the PR description body (not just the title). GitHub will auto-close the issue when the PR merges.
For partial progress, use Related to #N instead.
If you discover new work during implementation (bugs, follow-ups, tech debt), create a GitHub Issue:
gh issue create --title "Brief description" --label "label" --body "Details"
There is no TODO.md in this repository. All tracking lives in GitHub Issues.
AGENTS.md — Contains the GitHub Issues tracking rule