Repository navigation
Add missing_capability issue to alexandria feedback - #272
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
No issues found across 5 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Shadow auto-approve: would require human review. Adds missing_capability as a valid issue code for --capability-feedback, extending the request contract and relying on companion API/DB changes; needs human sign-off on API/data semantics and deployment coordination.
Re-trigger cubic
There was a problem hiding this comment.
0 issues found across 1 file (changes from recent commits).
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Shadow auto-approve: would require human review. Adds missing_capability as a new accepted capability-feedback issue code, extending the request contract and depending on companion API/database changes; needs human sign-off on contract semantics and deployment coordination.
Re-trigger cubic
What changed
firecrawl alexandria feedback:--capability-feedbacknow accepts the newmissing_capabilityissue code (the provider exists but lacks this capability). It is accepted with or withoutrequestedFunctionality.new_capability_requeststill requiresrequestedFunctionality; unknown issue codes are still rejected before anything is posted.--capability-feedbacklists the new code with its meaning.firecrawl alexandria feedbacksection now enumerates the capability issue codes;skills/firecrawl-agent/SKILL.mdgets a one-line hint on when to usemissing_capabilityvsnew_capability_request.parseAlexandriaFeedbackArray(accepted with/withoutrequestedFunctionality,new_capability_requeststill rejected without it, unknown code still rejected) and an end-to-end case asserting the CLI postsmissing_capabilitytoPOST /v2/feedbackunchanged.Context
Pairs with the API change that moves Alexandria feedback into dedicated tables server-side and extends
capabilityFeedback[].issuewithmissing_capability:No client-visible change to the request shape other than the new issue value. No version bump or changelog entry (the repo has none).
Test plan
pnpm install --frozen-lockfile,pnpm build(tsc): passpnpm format/pnpm format:check: cleanpnpm test(vitest): 34 files, 592 tests passpnpm vitest run src/__tests__/commands/feedback.test.ts src/__tests__/alexandria-beta.test.ts -t "missing_capability|malformed": passSummary by cubic
Adds
missing_capabilityas a valid issue code forfirecrawl alexandria feedback --capability-feedback, so users can report when a provider exists but lacks the needed capability. It's accepted with or withoutrequestedFunctionality;new_capability_requeststill requires it, and unknown codes are still rejected before anything is posted.Docs and tests
--capability-feedbackhelp text, README, andSKILL.mdto list the new code.requestedFunctionalityrequirement, and rejection of unknown codes.1.24.1.Written for commit 2536c85. Summary will update on new commits.