com um clique
source-layout-validation-sweep
// Update CI validation and smoke-test surfaces when source trees move but root entrypoints must keep working
// Update CI validation and smoke-test surfaces when source trees move but root entrypoints must keep working
{what this skill teaches agents}
Structure public Rust crate docs so docs.rs reads as both a quick-start guide and an API reference
Refactor Rust crates toward httprunner-style bounded-context directories with thin mod.rs facades.
Validate internal Rust module splits without accidentally treating them like feature work.
Automated workflow patterns for publishing Rust crates to crates.io from GitHub Actions, including version injection, token auth, and multi-crate dependency ordering.
Update documentation after a source-tree move without breaking repo-root command guidance
| name | source-layout-validation-sweep |
| description | Update CI validation and smoke-test surfaces when source trees move but root entrypoints must keep working |
| domain | testing |
| confidence | high |
| source | observed |
Use this when a repository reorganizes source folders (for example into src\...) without changing the public root-invoked build/test commands. The risky part is usually not the business logic; it is the workflow triggers, solution paths, packaging copies, and smoke-test assumptions that still point at the old folders.
paths: filters first so CI still runs when moved source changes.target\release..sln files or manifest locations).src\dotnet can keep or break relative paths depending on how many levels they previously climbed.Directory.Build.props need extra scrutiny because relative Include= paths may be evaluated from consuming project directories, not just from the props file location.publish-manifest.json using ../docs/Marketplace.md does not survive a move from legacy\ to src\dotnet\; it must become ../../docs/Marketplace.md.target\... via parent-directory climbing, verify the climb depth still reaches the real repo root from the new location and hand off any fix to implementation owners when production-code edits are out of scope.crates/** to src/rust/**.legacy/** to src/dotnet/**.dotnet build legacy\HttpGenerator.sln to dotnet build src\dotnet\HttpGenerator.sln.target\release\httpgenerator(.exe) bundle paths unchanged when root cargo behavior is intentionally preserved.target\release assumptions unless the migration explicitly changes the root cargo contract.