engineering
Skill0 starsChanged 3 months agoMITView on GitHub
Orchestrate production software delivery through specification, repository intelligence, implementation, testing, security review, data operations, and release evidence. Use for substantial code changes that cross files, systems, or deployment boundaries.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- wubinKKK/private-ai-workbenchtheir own version, first seen Nov 8, 2026
- HsuanYuLee/polaristheir own version, first seen Nov 5, 2026
- wellwelwel/lagunetheir own version, first seen Oct 31, 2026
- PhoenixNest/AGENT-GLOBAL-BASEtheir own version, first seen Oct 20, 2026
- iammrduncan/skillstheir own version, first seen Oct 15, 2026
- wellwelwel/pokutheir own version, first seen Oct 8, 2026
Used with
Projects with it also use testing.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
NVIDIASkilltesting
Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- wellwelwel/poku★ 1.2ksame name
- wellwelwel/lagune★ 177same name
- HsuanYuLee/polaris★ 5same name
- iammrduncan/skills★ 4same name
- wubinKKK/private-ai-workbench★ 4same name
- eXodes/skills-workspace★ 3same name
- PhoenixNest/AGENT-GLOBAL-BASE★ 2same name
- Dhi13man/skivolve★ 1same name
- modeled-information-format/mif-docs-plugin★ 1same name
- Patasse97/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- code-intelligenceSkill
- engineering-deliverySkill
- skill-security-auditSkill
- supabase-operationsSkill
- video-workbenchSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Use code-intelligence to map architecture and impact before editing unfamiliar or cross-cutting code.
- Very specific: line 18
Use engineering-delivery as the lifecycle owner: plan small slices, implement, test, review, and report.
- Very specific: line 20
Run skill-security-audit before importing unfamiliar executable skills or dependencies.
- Distinctive: line 21
Keep an evidence ledger: commands, results, artifacts, regressions checked, and remaining risk.
- Distinctive: line 41
Read references/routing.md and references/output-contract.md.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Engineering
Designed, integrated, refactored, and continuously maintained by TIKAZ.
Inputs and routing
Accept a repository, requested change, constraints, risk boundary, and expected evidence. Use the orchestrator for cross-file or release-bound work; use a child Skill directly when architecture mapping, delivery, security audit, Supabase operations, or media-pipeline engineering is the whole outcome.
TIKAZ method
- Freeze scope, non-goals, acceptance criteria, and evidence required for completion.
- Use
code-intelligenceto map architecture and impact before editing unfamiliar or cross-cutting code. - Use
engineering-deliveryas the lifecycle owner: plan small slices, implement, test, review, and report. - Route only domain-specific work to
supabase-operationsorvideo-workbench. - Run
skill-security-auditbefore importing unfamiliar executable skills or dependencies. - Keep an evidence ledger: commands, results, artifacts, regressions checked, and remaining risk.
Conflict rule
code-intelligence advises; engineering-delivery executes. Domain adapters cannot expand scope without explicit acceptance criteria.
Completion gate
Require repository-native validation, final diff review, no leaked secrets, an explicit release/rollback note when applicable, and objective evidence for every acceptance criterion.
Output, fallback, and limits
Return the agreed scope, impact map, implementation record, verification evidence, rollback note, and remaining risks. If repository-native commands or required credentials are unavailable, stop at the last verified artifact and state the missing capability. Do not deploy, migrate production data, or perform destructive actions without explicit authority.
Example
Use engineering to map this API change, implement it in small verified slices, review the final diff, and provide rollback evidence.Read references/routing.md and references/output-contract.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.