Slash command ek Markdown file hai jiska mukhya bhaag seedha prompt ban jaata hai. Ek hi request baar-baar type karna band karne ka ye sabse saral tareeka hai — ek review, release se pehle ki jaanch, aapki team jis roop mein summary chahti hai wahi — aur poori configuration mein sabse kam nakhre wala hissa bhi. Bigadta sirf ek jagah hai: arguments. Command ke naam ke baad type kiya sab kuchh ek placeholder ke roop mein aata hai, alag-alag shabd numbered placeholders ke roop mein; aur jo mukhya bhaag inme se kisi ka zikr nahi karta, wo user ke diye input ko ignore karte hue bhi ye declare karta rehta hai ki wo kuchh leta hai. Ye builder file likhta hai, placeholders buttons ke roop mein deta hai, aur is bemel ko dono taraf se batata hai.
Features
Placeholders yaad rakhne ke bajaye button se daale jaate hain
Argument ka elaan ho par prompt use na kare to warning
Prompt argument leta ho par user ko kuchh na bataya gaya ho to warning
Optional tools list aur model chunav
Naam file-name ki tarah check hota hai — wo banta bhi wahi hai
Project ya personal scope, saath mein upyukt path
Command kaise type hoga uski jhalak
Seedhe use layak .md file ke roop mein download
Slash Command Builder kaise use karein
Command ka naam rakhiye — wahi /naam bhi hai aur file ka naam bhi
Jahaan input aana hai wahaan $ARGUMENTS ya $1 daalkar prompt likhiye
Argument hint jodiye taaki user jaane ki kya dena hai
Scope chuniye aur file download kijiye
Example
Input
argument-hint: <pr-number>
Output
Review pull request #$1.
Hint aur placeholder mel khane chahiye, warna dono mein se ek jhooth hai.
Common errors aur troubleshooting
Command uske baad type ki gayi baat ko ignore kar deta hai. — Mukhya bhaag ko input use karna hoga. $ARGUMENTS poora type kiya hua hai; $1, $2 aur $3 alag-alag shabd hain.
Command list mein dikhta hi nahi. — File ka naam hi command ka naam hai, isliye lowercase aur hyphen chahiye, aur file chune hue scope ki commands directory mein honi chahiye.
List mein description nahi aa raha. — Wo frontmatter ke description field se aata hai. Uske bina command bina naam-patti ke dikhta hai.
$1 aur $ARGUMENTS ek-doosre par chadhte lagte hain. — Chadhte hi hain: $ARGUMENTS mein sab kuchh hai, $1 uska pehla shabd. Jab tak dono jaan-boojhkar na chahiye, ek hi lijiye.
Aksar pooche jaane wale sawaal
$ARGUMENTS aur $1 mein kya farq hai?
$ARGUMENTS command ke naam ke baad type ki poori line hai. $1, $2 aur $3 space se alag hue shabd hain. Command tay sankhya mein inputs leta ho to numbered, aur khula text leta ho to $ARGUMENTS.
Kya allowed tools ki list chahiye?
Nahi, aur adhiktar commands mein hoti bhi nahi. Ye tab saarthak hai jab koi command har baar poochhe bina kuchh khaas chala sake, ya jab aap chahein ki wo wo na kar sake jo session waise kar sakta hai.
Command file kahaan rehti hai?
Project ka command repository mein rehta hai taaki poori team ko mile; personal aapke saath projects mein chalta hai. Sateek path dikhta hai aur naam ke saath badalta hai.
Kya command tools bula sakta hai?
Mukhya bhaag ek prompt hai, isliye wo har wo cheez maang sakta hai jo session pehle se kar sakta tha. Tools list sirf ye ghatati-badhati hai ki bina poochhe kya chale; naya adhikaar wo nahi deti.
Skill ke bajaye command kab banayein?
Command type karke jaan-boojhkar bulaya jaata hai. Skill tab apne aap judti hai jab koi kaam prasangik lage. Samay aap tay karna chahte hain to command likhiye; apne aap ho jaaye ye chahte hain to skill.