Repository navigation
docs: regenerate rules from documentation@2cfb813 - #121
Merged
Merged
Conversation
Sync-Repaired: {"skill":"harper-best-practices","rule":"schema-design-tooling","repairs":1,"restored":["@embed","[Float]","model","source"],"fixed":[]}
Sync-Repaired: {"skill":"harper-best-practices","rule":"automatic-apis","repairs":1,"restored":["HEAD","QUERY","connect()"],"fixed":[]}
Sync-Repaired: {"skill":"harper-best-practices","rule":"v5-upgrade","repairs":1,"restored":["applications.allowedSpawnCommands","dependencyLoader: native"],"fixed":[]}
Sync-Repaired: {"skill":"harper-mcp","rule":"enabling-mcp","repairs":1,"restored":["initialize","mcpResources"],"fixed":[]}
dawsontoth
approved these changes
Oct 7, 2026
|
🎉 This PR is included in version 1.14.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated regeneration of docs-driven skill rules, now synced to
HarperFast/documentation@2cfb813.Why these rules changed
This PR changes each rule below relative to
main, where it was last synced from the docs commit shown. The trigger commit is not necessarily what changed a given rule — drift accumulates across every docs commit since the rule’s recorded baseline (below).automatic-apis— last synced from docs@677ad21deploying-to-harper-fabric— last synced from docs@677ad21extending-tables— last synced from docs@ce0ab71handling-binary-data— last synced from docs@ce0ab71querying-rest-apis— last synced from docs@677ad21schema-design-tooling— last synced from docs@677ad21using-blob-datatype— last synced from docs@f37a8c4v5-upgrade— last synced from docs@677ad21enabling-mcp— last synced from docs@d7d2ddbDocs commits since baseline (
ce0ab71..2cfb813)Repaired during generation
The first regeneration of these rules failed its checks, and a repair pass fixed it. Check that each restored fact landed where it belongs.
automatic-apis— 1 repair: restoredHEAD,QUERY,connect()schema-design-tooling— 1 repair: restored@embed,[Float],model,sourcev5-upgrade— 1 repair: restoredapplications.allowedSpawnCommands,dependencyLoader: nativeenabling-mcp— 1 repair: restoredinitialize,mcpResourcesProduced by
.github/workflows/generate.yaml. Review the diff as you would any rule change — the generator reads the docs build output and rewritesmode: generate/ importsmode: directrule bodies, then reassembles AGENTS.md. See docs/plans/docs-driven-skills.md.🤖 Generated with Claude Code