You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add SPFx Fast SharePoint development skill 🤖🤖🤖 - #5992
Risk tier:merge-risk:high — Privileged execution, automation, or review-policy change Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access, including a maintainer with admin or maintain permission.
Why this tier
Label needs-review:HIGH flags a high contributor-risk signal
3. Choose a starter with `pnpm exec spfx-fast use-cases` or `pnpm exec spfx-fast scenarios`. With npm, use `npx --no-install spfx-fast`. Generate only after inspecting the target s
🟠
package-exec-command
skills/spfx-fast/SKILL.md
20
With npm, replace `pnpm exec` with `npx --no-install`.
🟠
package-exec-command
skills/spfx-fast/SKILL.md
21
4. Run `pnpm exec spfx-fast agent init` and `pnpm exec spfx-fast agent doctor`. With npm, use `npx --no-install spfx-fast`. Doctor checks local setup, not tenant permissions.
This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.
✓ [spec-compliance] All 1 skill(s) are spec-compliant.
ℹ️
✓ spec-compliance: All spec checks passed.
ℹ️
✓ [valid-refs] All file references across 1 skill(s) are valid.
ℹ️
✓ valid-refs: All file references resolve to existing files within the skill directory.
ℹ️
1 skill(s) linted, 1 passed
Full linter output
### Linting skills/spfx-fast
✅ spfx-fast (2/2 checks passed)
✓ [spec-compliance] All 1 skill(s) are spec-compliant.
✓ spec-compliance: All spec checks passed.
✓ [valid-refs] All file references across 1 skill(s) are valid.
✓ valid-refs: All file references resolve to existing files within the skill directory.
1 skill(s) linted, 1 passed
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
The documented bare CLI commands fail without a global installation because the project-local executable is not on the shell PATH; they need a project-local runner.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The instructions reference an incorrect project-root path for the installed package’s capabilities file, which can cause setup to fail or load the wrong file and must be corrected.
No open issues 🎉
1 previously missed issue
In code that hasn't changed since last review
Resolve capabilities.json from the installed package
skills/spfx-fast/SKILL.md:13
After @spfx-fast/core is installed in an SPFx project, agent/capabilities.json is not a project-root path; the package ships this file under node_modules/@spfx-fast/core/agent/capabilities.json. Following this instruction can fail or load an unrelated local file before coding. Use the package-qualified path for both files (or otherwise resolve the installed package root).
This issue also appears in the following locations of the same file:
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The guide still needs corrections for awaiting and initializing createSPFxServices and for documenting the required Graph delegated scopes and admin consent, since otherwise generated code may fail at runtime or receive 403 responses.
No open issues 🎉
2 previously missed issues
In code that hasn't changed since last review
Await createSPFxServices before accessing service clients
skills/spfx-fast/SKILL.md:22
createSPFxServices is asynchronous (it awaits the SPFx Graph client), so omitting await here can cause generated code to use a Promise as services and fail at runtime. State that the services must be awaited and initialized once per web part before accessing client, sharepoint, or rest.
Add Graph scope and admin consent setup
skills/spfx-fast/SKILL.md:23
The generated dashboard's list helpers use Graph, but SPFx still requires the corresponding delegated scopes in config/package-solution.json and admin consent; otherwise the advertised Graph reads/writes fail with 403 even though createSPFxServices is authenticated. The current steps only say to preserve permission checks, so add an explicit scope/consent step before telling the agent to test or ship the generated app.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
Human assessment is needed because the review uncovered a moderate path-documentation issue in the SPFx setup instructions that could prevent agents from loading the package capability and scope limits.
This skill is just a wrapper around skill sourced externally, which we don't support in this repo as it poses a security supply chain risk.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The skill is also installable directly from
vystartasv/spfx-fastwith:Validation
npm run skill:validatenpm start🤖🤖🤖