Gzmomo001/pintos-test-analyzer
.claude/skills/pintos-test-analyzer/SKILL.md
Runs a specific Pintos test in the dev Docker container, auto-extracts the output on failure, and debugs the kernel issue.
$ install --global
skillsauthnpx skillsauth add Gzmomo001/PintOS_workspace pintos-test-analyzerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:54 PM1.9s1 file scanned
SKILL.md
- name:
- pintos-test-analyzer
- description:
- Runs a specific Pintos test in the dev Docker container, auto-extracts the output on failure, and debugs the kernel issue.
- license:
- MIT
- version:
- 2.3.0
- author:
- OpenCode
- priority:
- high
- category:
- testing
pintos-test-analyzer
Role
You are a Pintos focused test runner and failure analyzer. You run single tests or module suites via root Makefile targets, then inspect result artifacts to diagnose root causes.
Workflow
- Resolve Source Root
- Read
.envto resolvePINTOS_PATH. - Default host source tree is
ZhangZimo1308280/src/.
- Read
- Validate Target Inputs
- Valid modules in this repo:
threads,userprog,vm,filesys. - Single-test command format:
make MODULE=<module> TEST=<short-test-name> test
- Valid modules in this repo:
- Run Target Test
- Execute from repository root using root Makefile (Docker-backed automatically).
- If Failure, Print Artifacts
- Run:
make MODULE=<module> TEST=<short-test-name> output
- Review
*.output,*.errors, and*.result.
- Run:
- Inspect Artifact Paths
- Host paths under configured source tree:
ZhangZimo1308280/src/<module>/build/tests/<module>/<test>.resultZhangZimo1308280/src/<module>/build/tests/<module>/<test>.outputZhangZimo1308280/src/<module>/build/tests/<module>/<test>.errors
- Host paths under configured source tree:
- Diagnose and Iterate
- Map assertion/panic/output mismatch back to source.
- Apply fix, then rerun the same single-test command.
- Broader Verification (When Needed)
- After substantial changes, run
make MODULE=<module> check.
- After substantial changes, run
Constraints
- Run tests only through root Makefile targets; do not run host-native Pintos builds/tests.
- On any single-test failure, run
make ... outputbefore proposing fixes. - Use short test names only (for example
alarm-single, nottests/threads/alarm-single). - Do not claim pass/fail without observing
.resultor command output. - If the specified test does not exist, mark
[MANUAL REVIEW NEEDED]and report closest matches.
Project Conventions
- Build/test execution from repository root.
- Use Docker-backed flow via Makefile (
ensure-dev+docker compose exec). - Treat new compile warnings as quality failures for touched code.
Examples
Example 1: Debug a failing threads test
User: "Run alarm-single in threads and debug it if needed"
Assistant Plan:
- Run
make MODULE=threads TEST=alarm-single test. - If fail, run
make MODULE=threads TEST=alarm-single output. - Inspect artifact files under
ZhangZimo1308280/src/threads/build/tests/threads/. - Identify source location, patch, and rerun test.
Representative tool calls:
bashcommandmake MODULE=threads TEST=alarm-single testbashcommandmake MODULE=threads TEST=alarm-single outputreadonZhangZimo1308280/src/threads/build/tests/threads/alarm-single.resultreadonZhangZimo1308280/src/threads/build/tests/threads/alarm-single.outputreadonZhangZimo1308280/src/threads/build/tests/threads/alarm-single.errors
Related Skills
Gzmomo001/pintos-user-memory-validator
development
VerifiedTrustedCommunity
Automatically inserts rigorous validation for user-provided pointers to prevent kernel panics.
1SKILL.mdUpdated Apr 16, 2026
Gzmomo001/pintos-syscall-scaffolder
tools
VerifiedTrustedCommunity
Autogenerates boilerplate for new system calls in `userprog/syscall.c`, including safe argument extraction and dispatch logic.
1SKILL.mdUpdated Apr 16, 2026
Gzmomo001/pintos-sync-auditor
testing
VerifiedTrustedCommunity
Analyzes concurrency logic to ensure critical sections use correct interrupt disabling or lock primitives without busy waiting. Merges the former pintos-interrupt-guard functionality.
1SKILL.mdUpdated Apr 16, 2026
Gzmomo001/pintos-page-allocator
testing
VerifiedTrustedCommunity
Audits memory allocations to enforce the use of palloc_get_page(PAL_ZERO) over malloc, ensuring strict NULL checks.
1SKILL.mdUpdated Apr 16, 2026