redditreddit/suitereact-mcp/.agents/skills/suitereact-commit/SKILL.md

suitereact-commit

Skill14 starsChanged 13 days agoBSD-3-ClauseView on GitHub

Safely commits a verified SuiteReact workflow by checking the target branch and staging only exact files owned by that workflow. Use to finalize SuiteReact app work without pushing.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific
could be automatic: a setting could enforce it

Distinctive:
Run autonomously, but never push unless explicitly requested.
line 10
Very specific:
Verify the active branch equals targetBranch.
line 13
Very specific:
Never run git add apps/<app>/, git add ., or stage ignored workflow artifacts.
line 21

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Commit SuiteReact work

Usage: /suitereact-commit <app-name> --workflow-dir <path>

Run autonomously, but never push unless explicitly requested.

Require workflow.json phase ready_to_commit, passing required checks, and a non-empty ownedFiles list.
Verify the active branch equals targetBranch. Do not infer a different destination from a temporary worktree name. The staging command reports when the target branch is checked out in another worktree.
Stage and verify only workflow-owned files:

npm run workflow -- stage <workflow-dir>
npm run workflow -- verify-stage <workflow-dir>

Never run git add apps/<app>/, git add ., or stage ignored workflow artifacts. Existing staged files outside ownership are blocking; preserve them and report the exact paths.

Review git diff --cached --stat and git diff --cached. Commit with an accurate conventional subject and this body metadata:

Workflow: <workflow-id>

Record the resulting SHA after the commit:

npm run workflow -- finalize-commit <workflow-dir>

Report the branch, SHA, and exact committed files.

Download now (ZIP)

In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/global.mdcCursor rule
- .cursor/rules/netsuite-integration.mdcCursor rule
- .cursor/rules/react-patterns.mdcCursor rule
- doc-spaces-authorSkill
- doc-spaces-publishSkill
- doc-spaces-searchSkill
- suiteql-cookbookSkill
- suitereact-analyzeSkill
- suitereact-codeSkill
- suitereact-deploySkill
- suitereact-devSkill
- suitereact-full-cycleSkill
- suitereact-reviewSkill
- suitereact-scaffoldSkill
- suitereact-test-actionSkill
- suitereact-testSkill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free