— No reviews yet
0 installs
3 views
0.0% view→install
Install
$ agentstack add skill-mattjaikaran-meridian-debug ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Are you the author of Debug? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claimAbout
/meridian:debug — Systematic Debugging
4-phase systematic debugging with decision logging. Uses the protocol from references/discipline-protocols.md.
Arguments
- `` — Bug description or error message
--plan— Associate with a specific plan--phase— Associate with a specific phase
Procedure
Phase 1: Investigation
- Read the full error message and stack trace
- Identify the exact file, line, and function
- Check recent changes:
git log --oneline -10andgit diff - Reproduce the error by running the failing test/command
- Record findings
Phase 2: Pattern Recognition
- Categorize the error type:
- Import/module error
- Type error / null reference
- Logic error / wrong behavior
- Race condition / timing
- Configuration / environment
- Data integrity
- Search codebase for similar patterns
- Check if this is a known issue pattern
Phase 3: Hypothesis
- Form a specific hypothesis: "The error occurs because X"
- Identify evidence that would confirm/refute
- Test with minimal change
- Record hypothesis and result as a decision:
PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c "
from scripts.db import connect, get_db_path
from scripts.state import create_decision
conn = connect(get_db_path('.'))
create_decision(conn, '', category='approach',
rationale='', phase_id=)
conn.close()
"
Phase 4: Implementation
- Fix at the source, not the symptom
- Run the failing test — must pass now
- Run full test suite — no regressions
- Commit the fix with descriptive message
Escalation Rule
After 3 failed fix attempts:
- STOP fixing
- Record a deviation decision
- Re-examine assumptions
- Consider if the problem is architectural
- May need to re-plan the current phase
PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c "
from scripts.db import connect, get_db_path
from scripts.state import create_decision
conn = connect(get_db_path('.'))
create_decision(conn, 'Escalation: 3+ failed fixes on . Likely architectural.',
category='deviation', rationale='')
conn.close()
"
Output
Report:
- Root cause identified
- Fix applied (file:line)
- Tests passing
- Decision logged
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mattjaikaran
- Source: mattjaikaran/meridian
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.