affaan-m/ecc

project-flow-ops

Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/affaan-m/ecc --skill project-flow-ops

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Project Flow Ops

This skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.

Use it when the problem is coordination, not coding.

When to Use

  • Triage open PR or issue backlogs
  • Decide what belongs in Linear vs what should remain GitHub-only
  • Link active GitHub work to internal execution lanes
  • Classify PRs into merge, port/rebuild, close, or park
  • Audit whether review comments, CI failures, or stale issues are blocking execution

Operating Model

  • GitHub is the public and community truth
  • Linear is the internal execution truth for active scheduled work
  • Not every GitHub issue needs a Linear issue
  • Create or update Linear only when the work is:
  • active
  • delegated
  • scheduled
  • cross-functional
  • important enough to track internally

Core Workflow

1. Read the public surface first

Gather:

  • GitHub issue or PR state
  • author and branch status
  • review comments
  • CI status
  • linked issues

2. Classify the work

Every item should end up in one of these states:

StateMeaning
Mergeself-contained, policy-compliant, ready
Port/Rebuilduseful idea, but should be manually re-landed inside ECC
Closewrong direction, stale, unsafe, or duplicated
Parkpotentially useful, but not scheduled now

3. Decide whether Linear is warranted

Create or update Linear only if:

  • execution is actively planned
  • multiple repos or workstreams are involved
  • the work needs internal ownership or sequencing
  • the issue is part of a larger program lane

Do not mirror everything mechanically.

4. Keep the two systems consistent

When work is active:

  • GitHub issue/PR should say what is happening publicly
  • Linear should track owner, priority, and execution lane internally

When work ships or is rejected:

  • post the public resolution back to GitHub
  • mark the Linear task accordingly

Review Rules

  • Never merge from title, summary, or trust alone; use the full diff
  • External-source features should be rebuilt inside ECC when they are valuable but not self-contained
  • CI red means classify and fix or block; do not pretend it is merge-ready
  • If the real blocker is product direction, say so instead of hiding behind tooling

Output Format

Return:

text
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

Good Use Cases

  • "Audit the open PR backlog and tell me what to merge vs rebuild"
  • "Map GitHub issues into our ECC 1.x and ECC 2.0 program lanes"
  • "Check whether this needs a Linear issue or should stay GitHub-only"

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills
affaan-m
社区

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

24小时安装量
489
GitHub Stars
30.8万
最近更新
11月20日
affaan-m
社区

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

1小时安装量
5
GitHub Stars
30.8万
最近更新
11月20日
affaan-m
社区

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

1小时安装量
2
GitHub Stars
30.8万
最近更新
11月20日
affaan-m
社区

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1小时安装量
2
GitHub Stars
30.8万
最近更新
11月20日