mirror of
https://github.com/wesammustafa/opencode-primer.git
synced 2026-11-18 18:04:22 +00:00
markdownlint - Disable MD028 (no-blanks-blockquote): we intentionally separate adjacent blockquote callouts (a tip + a warning side-by-side) with a blank line; visually this renders as two callouts, which is the intent. - Switch MD029 (ol-prefix) to "one_or_ordered": both "1. / 2. / 3." and "1. / 1. / 1." (auto-renumber) are valid; the rule was hitting ordered lists that have intervening code blocks, where the lint loses count. - Add blank lines before lists in five places where MD032 fired (test.md, git-release/SKILL.md, agents.md, skills.md, migration.md). - Fix nested code-fence bug in database-engineer-prompt.md: the outer ``` was being closed by an inner ```sql; switched the outer fence to ```` (4 backticks) so the inner one stays nested. link-check - Ignore https://mcp.grep.app and https://ai.google.dev/ — the first returns 405 to HEAD requests (verified working via GET); the second trips an infinite-redirect bug in the link checker (real URL works). - Ignore github.com/anomalyco/opencode/discussions — the upstream repo currently has discussions disabled. - Add 405 to aliveStatusCodes for endpoints that accept GET but reject HEAD.
1018 B
1018 B
description, agent
| description | agent |
|---|---|
| Run the project test suite and triage any failures | build |
Run the project test suite and triage failures.
- Detect the runner from the repo and run it:
!cat package.json 2>/dev/null | grep -E '"test"|"scripts"' | head -5
Pick the right command:
pnpm test,npm test,yarn testfor Nodepytest/python -m pytestfor Pythongo test ./...for Gocargo testfor Rust- Other: read the project's
AGENTS.mdfor the canonical command
- Run it and capture the output:
!{the chosen test command}
-
If everything passes, print a one-line summary and stop.
-
If there are failures:
- Group them by file
- For each failing test, open the relevant source and identify the root cause
- Propose a fix (snippet) but do not edit files yet — wait for user approval
- Distinguish between "test is wrong" and "code is wrong"
-
After the user confirms, apply the fixes and re-run the suite to verify.
Extra arguments (passed to the runner): $ARGUMENTS