AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Ci Fix

skill-d-o-hub-rust-self-learning-memory-ci-fix · by d-o-hub

Diagnose and fix GitHub Actions CI failures for Rust projects. Use when CI fails, tests timeout, or linting issues occur. Captures common patterns from CLAUDE_INSIGHTS_REPORT.md.

No reviews yet
0 installs
41 views
0.0% view→install

Install

$ agentstack add skill-d-o-hub-rust-self-learning-memory-ci-fix

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-d-o-hub-rust-self-learning-memory-ci-fix)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Ci Fix? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

CI Fix Skill

Diagnose and fix GitHub Actions CI failures using patterns from past CI issues.

Quick Diagnosis Pattern

  1. Get CI status:
gh run list --limit 5 --json status,conclusion,name,headBranch
  1. Get failed job logs:
gh run view  --log --job 
  1. Categorize failure:
  • lint: fmt/clippy warnings
  • test: test failures or timeouts
  • build: compilation errors
  • security: cargo audit/deny failures
  • coverage: coverage threshold missed
  • deprecated: old action versions (common!)

Common Fixes (From History)

Deprecated GitHub Actions

# Detect
grep -r "actions/checkout@v1" .github/workflows/
grep -r "actions-rs" .github/workflows/

# Fix: Update to v2+

Optional Dependency Issues (libclang, wasmtime)

# Pattern: --all-features triggered optional dep issues
# Fix: Use workspace exclude
cargo build --workspace --exclude do-memory-mcp

Clippy Lint Allow-List

# See new warnings
./scripts/code-quality.sh clippy --workspace 2>&1 | grep "warning:"

# Fix: Add #[allow(...)] comments

Coverage Threshold

# Generate coverage
cargo tarpaulin --workspace

# Check threshold in .github/workflows/

Benchmark Timeout

# Increase timeout-minutes in workflow YAML

Fix Commands

# Linting
cargo fmt --all
cargo clippy --workspace --fix --allow-dirty

# Testing
cargo test --workspace -- --nocapture

# Security
cargo audit
cargo deny check

# Build
cargo build --workspace

Success Criteria

  • All CI jobs pass
  • No new warnings introduced

Codecov Patch Coverage Gap Fix

When Codecov reports "Patch coverage is X% with N lines missing coverage":

Step 1: Parse the Report

Identify files with missing lines from the Codecov comment:

| File | Patch % | Missing Lines |
|------|---------|---------------|
| path/to/file.rs | 0.00% | 24 Missing |

Step 2: Locate Uncovered Code

For each file, read the specific lines identified. They are typically:

  • New functions without tests
  • Extracted submodules (refactored code moved to new files)
  • Changed branches not exercised by existing tests

Step 3: Write Targeted Tests

Add tests to the existing #[cfg(test)] mod tests in each file, or to a sibling test file:

  • For new public functions: unit test exercising the function directly
  • For new structs: test Default, Debug, Clone impls + key methods
  • For refactored code: test that the extracted module works identically to before
  • For branch coverage: test each match arm / if-else branch

Step 4: Verify

cargo nextest run -p  -E 'test()'
cargo clippy --workspace -- -D warnings

Step 5: Commit

Single atomic commit: test(coverage): add tests for Codecov patch gaps in N files

Common Patterns

  • Extracted submodule (e.g. stats.rs from wrapper.rs): test the new module's public API directly
  • New monitoring metric: test the recording method + snapshot/getter
  • New heuristic function: test boundary conditions (empty input, short/long input, edge cases)
  • New StorageType enum: test Debug, Clone, and pattern matching
  • Changes committed if needed

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.