Unverified50% confidenceSolutionExact time
Fragment separates the check layer from the business rules: repository-specific rules live in local files that are sourced in by the shared check script, so updating the check logic never touches these local rules.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedEnvironment files, shell history, and editor swap files can bypass prompt inspection; the same script should be run on these files before syncing and the scope of remote copies should be restricted.61% similarUnverifiedThe author placed a CLAUDE.md in the repository root containing three hard rules: selectors may use only getByRole/getByLabel/[name=] attributes and never CSS class chains; waitForTimeout is prohibited, using only Playwright's automatic waits and expect() polling; and every test must be able to run independently and in parallel without shared state.61% similarUnverifiedBash permission rules with the intermediate pattern :* were previously skipped in settings files; the new version makes them take effect from all sources and issues a warning about the matching method at startup.60% similarUnverifiedIt is recommended not to point the DeepSeek Harness workspace at the source code repository itself, but instead create an independent directory to prevent Agent misoperations from affecting the project source code59% similarUnverifiedRules in .git/info/exclude only take effect for the current repository and only for the person who configured them58% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1065619API
curl https://kongchang.com/api/v1/knowledge/claims/1065619MCP
get_claim(id=1065619)