resync
Skill0 starsChanged 2 days agoMIT-0View on GitHub
Synchronizes repository state, ACCC metrics, invariant gates, and hardware PMU benchmark JSON reports after manual or ad hoc code edits. Use this skill when resyncing the project after manual edits or before starting an orchestrator workflow.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- pietz/skillstheir own version, first seen Nov 8, 2026
- stormlightlabs/miretheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- pietz/skills★ 2same name
- stormlightlabs/mire★ 1same 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.
- architectSkill
- audit-sansSkill
- audit-staticSkill
- featureSkill
- performanceSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use this workflow after manual IDE edits or ad hoc fixes outside the strategic architect loop to bring all JSON telemetry, hardware PMU …
- Very specific: line 14
Run the deterministic introspection script to measure exact token footprints, extract CMakeLists.txt dependency edges, calculate subagent …
- Very specific: line 32
If C++ translation units or headers under targets/ were modified, verify static analysis and dual compiler debug and release builds.
- Very specific: line 44
Run sync_manifest.py --check once more so dirty_benchmarks clears and production_artifacts/manifest.json reflects the freshly generated …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deterministic repository resync workflow
Use this workflow after manual IDE edits or ad hoc fixes outside the strategic architect loop to bring all JSON telemetry, hardware PMU reports, static analysis logs, and dual compiler builds back into parity.
Step 1. Recompute bottom up ACCC state and check hard invariant gates
Run the deterministic introspection script to measure exact token footprints, extract CMakeLists.txt dependency edges, calculate subagent sizing scores $\Psi(C_i)$, and evaluate hard gates $H_1$ through $H_5$.
python3 .agents/skills/architect/scripts/sync_manifest.py --checkFix any reported violation in H1_acyclicity, H2_anchor_preservation, H3_execution_verification_parity, H4_compiler_regime_and_insulation, or H5_context_locality before proceeding.
Step 2. Re-run dirty hardware PMU benchmarks
Inspect dirty_benchmarks in production_artifacts/manifest.json. For each listed component, execute its <name>BENCH_run target under Clang_Custom_Release to regenerate production_artifacts/profiling/<name>_score_report.json.
cmake --build --preset Clang_Custom_Release --target <name>BENCH_runStep 3. Reconcile static analysis and dual compiler verification
If C++ translation units or headers under targets/ were modified, verify static analysis and dual compiler debug and release builds.
cmake --preset Clang_Tidy && cmake --build --preset Clang_Tidy
./production_artifacts/build_all.sh custom debug
./production_artifacts/build_all.sh default releaseResolve any safety critical findings in code and update production_artifacts/clang_tidy_state.md if situational exceptions changed.
Step 4. Finalize manifest and commit clean state
Run sync_manifest.py --check once more so dirty_benchmarks clears and production_artifacts/manifest.json reflects the freshly generated <name>_score_report.json files. Commit all updated files so git status --porcelain is clean for subsequent architect or performance runs.
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.

