Coordinate GitHub and Linear workflows for triage, tracking, and execution alignment.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "project-flow-ops" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/project-flow-ops/SKILL.md 2. Save it as ~/.claude/skills/project-flow-ops/SKILL.md 3. Reload skills and tell me it's ready
Help me review GitHub issues and Linear tasks: identify work that should be created, in progress, blocked, or ready to close, and suggest how to sync them while keeping GitHub public-facing and Linear as the internal execution layer.
A clear triage result with status categories, missing links, and recommended sync actions.
Review the currently open GitHub pull requests, determine which should be linked to Linear tasks, which lack context, and which can be merged or need follow-up, then produce an action list.
An action list for each PR with status, linking recommendations, and next steps.
Create collaboration rules for our team across GitHub and Linear, including when issues should become Linear tasks, how PRs should backlink, what stays in GitHub, and what should be maintained only in Linear.
An actionable workflow guide that standardizes public tracking and internal execution management.
This skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.
Use it when the problem is coordination, not coding.
Gather:
Every item should end up in one of these states:
| State | Meaning |
|---|---|
| Merge | self-contained, policy-compliant, ready |
| Port/Rebuild | useful idea, but should be manually re-landed inside ECC |
| Close | wrong direction, stale, unsafe, or duplicated |
| Park | potentially useful, but not scheduled now |
Create or update Linear only if:
Do not mirror everything mechanically.
When work is active:
When work ships or is rejected:
Return:
PUBLIC STATUS
- issue / PR state
- CI / review state
CLASSIFICATION
- merge / port-rebuild / close / park
- one-paragraph rationale
LINEAR ACTION
- create / update / no Linear item needed
- project / lane if applicable
NEXT OPERATOR ACTION
- exact next move
Extract shared principles from skills and turn them into maintainable rule files.
Apply Django security best practices for safer auth, app defenses, and deployment.
Verify Laravel projects with environment checks, tests, security scans, and release readiness.
Get production-ready MySQL and MariaDB schema, query, and operations patterns.
Choose regex first, then add LLMs for low-confidence parsing edge cases.
Run repo tasks, debug CI, and deliver fixes with verified evidence.
Read, create, and update Linear issues, projects, and team workflows.
Manage Linear issues, projects, and team workflows with AI assistance
Manage Linear issues through one tool for search, updates, creation, and collaboration.
Collaboratively manage project docs, decisions, todos, pitfalls, and interfaces with AI.
Manage OpenProject projects, work packages, and progress reporting from Codex.
Connect to the Flow Team API via MCP for project and participant management.