Review inputs
- explicit boundaries
- stable contracts
- typed interfaces
affaan-m/ECC
Engineering operating model for teams where AI agents generate a large share of implementation output.
npx skills add https://github.com/affaan-m/ECC --skill "skills/ai-first-engineering"Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Limited to facts supported by the pinned source
Use this skill when designing process, reviews, and architecture for teams shipping with AI-assisted code generation.
npx skills add https://github.com/affaan-m/ECC --skill "skills/ai-first-engineering"The pinned source contains about 142 English words and 5 usable sections. That evidence supports a source profile, not a complete guide.
142 source words · 5 usable sections
Review inputs
What the source actually contains
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
1. Planning quality matters more than typing speed. 2. Eval coverage matters more than anecdotal confidence. 3. Review focus shifts from syntax to system behavior.
Review for: - behavior regressions - security assumptions - data integrity - failure handling - rollout safety
Prefer architectures that are agent-friendly: - explicit boundaries - stable contracts - typed interfaces - deterministic tests
Choose a different workflow
Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing b
A separate implementation from wshobson/agents; compare its source, maintenance signals, and permission requirements.
Open source detailCopilot left 14 review comments on your PR — half are nits. Hours of fix → reply → resolve → re-request, and each round lands MORE comments. This skill runs loop engineering: auto-triggers Copilot Code Review via GraphQL (no @copilot mention), triages every open thread (Copilot, humans, advanced-security) with a fix / decline / escalate rubric, dispatches parallel fix sub-agents that obey the repo build/test/lint conventions, commits per iteration, replies+resolves citing the pushed SHA, then re
A separate implementation from github/awesome-copilot; compare its source, maintenance signals, and permission requirements.
Open source detailMaster effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
A separate implementation from wshobson/agents; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
The source record exposes this install command: npx skills add https://github.com/affaan-m/ECC --skill "skills/ai-first-engineering". Inspect the command and pinned source before running it.
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Compare before choosing
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing b
Copilot left 14 review comments on your PR — half are nits. Hours of fix → reply → resolve → re-request, and each round lands MORE comments. This skill runs loop engineering: auto-triggers Copilot Code Review via GraphQL (no @copilot mention), triages every open thread (Copilot, humans, advanced-security) with a fix / decline / escalate rubric, dispatches parallel fix sub-agents that obey the repo build/test/lint conventions, commits per iteration, replies+resolves citing the pushed SHA, then re
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
Use when writing, validating, or preparing ANY contribution or pull request to the JSONbored/metagraphed repo — adding/enriching a subnet's public surfaces (the most common contribution), a code/schema change to the Worker API or build scripts, picking an issue, running the local gates, and formatting the commit + PR. metagraphed reviews PRs ONE-SHOT via the Gittensory Gate (the GitHub App that auto-merges/auto-closes) plus a strict CI suite; there is no review back-and-forth, so a PR must be co
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
Use this skill when designing process, reviews, and architecture for teams shipping with AI-assisted code generation.
Prefer architectures that are agent-friendly:
Avoid implicit behavior spread across hidden conventions.
Review for:
Minimize time spent on style issues already covered by automation.
Strong AI-first engineers:
Raise testing bar for generated code: