|
| 1 | +--- |
| 2 | +name: add-new-parser-or-provider |
| 3 | +description: Workflow command scaffold for add-new-parser-or-provider in periscope. |
| 4 | +allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"] |
| 5 | +--- |
| 6 | + |
| 7 | +# /add-new-parser-or-provider |
| 8 | + |
| 9 | +Use this workflow when working on **add-new-parser-or-provider** in `periscope`. |
| 10 | + |
| 11 | +## Goal |
| 12 | + |
| 13 | +Adds support for a new agent, data source, or provider to the system, including schema detection, discovery, and integration with sync and test coverage. |
| 14 | + |
| 15 | +## Common Files |
| 16 | + |
| 17 | +- `internal/parser/<agent>_provider.go` |
| 18 | +- `internal/parser/<agent>.go` |
| 19 | +- `internal/parser/types.go` |
| 20 | +- `internal/parser/provider.go` |
| 21 | +- `internal/parser/provider_migration.go` |
| 22 | +- `internal/parser/testdata/<agent>/*` |
| 23 | + |
| 24 | +## Suggested Sequence |
| 25 | + |
| 26 | +1. Understand the current state and failure mode before editing. |
| 27 | +2. Make the smallest coherent change that satisfies the workflow goal. |
| 28 | +3. Run the most relevant verification for touched files. |
| 29 | +4. Summarize what changed and what still needs review. |
| 30 | + |
| 31 | +## Typical Commit Signals |
| 32 | + |
| 33 | +- Implement parser/provider logic in internal/parser (e.g., <agent>_provider.go, <agent>.go) |
| 34 | +- Add/update types in internal/parser/types.go |
| 35 | +- Update provider registration in internal/parser/provider.go and/or provider_migration.go |
| 36 | +- Add test fixtures and coverage in internal/parser/testdata/<agent>/* and <agent>_test.go |
| 37 | +- Integrate with sync engine (internal/sync/engine.go, engine_test.go, integration_test.go) |
| 38 | + |
| 39 | +## Notes |
| 40 | + |
| 41 | +- Treat this as a scaffold, not a hard-coded script. |
| 42 | +- Update the command if the workflow evolves materially. |
0 commit comments